Skip to main content
Glama

CDF Finance

by io.github.VessellTech

Listar orçamentos

list_budgets
Read-only

Lista orçamentos (Budget) do usuário, mais recentes primeiro. Sem filtro retorna todos os períodos já criados (não só o mês atual). Cada item é o valor orçado; para orçado x gasto real de um orçamento específico use budget_comparison — para ver isso por categoria em todas as categorias de uma vez sem precisar de um Budget cadastrado, use categories_insights (insights.ts).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNoFiltra por ano (ex: '2026'). Se omitido junto com month, lista todos os anos
monthNoFiltra por mês (1-12). Só faz sentido combinado com year; orçamentos com period YEARLY não têm month

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / properties / month / description
      Added value: +"Filtra por mês (1-12). Só faz sentido combinado com year; orçamentos com period YEARLY não têm month"
    • addedInput schema / properties / year / description
      Added value: +"Filtra por ano (ex: '2026'). Se omitido junto com month, lista todos os anos"
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnlyHint annotation, the description discloses key behaviors: results are ordered most-recent-first, omitting filters returns all created periods (not just the current month), and each item is a budgeted amount. These details are not visible in the schema and add real operational context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences carry the action, ordering, default scope, item semantics, and two alternative-tool routes. No filler or repetition; each clause earns its place and the core behavior is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only listing tool with two optional parameters and an output schema, the description covers purpose, default behavior, nuance about monthly/yearly periods, and when to use alternative tools. Nothing needed to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents year and month well. The description adds the 'no filter returns all periods' behavior and that YEARLY budgets lack a month, but these mostly restate or lightly extend what the parameter descriptions and the main sentence imply.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Lista orçamentos (Budget) do usuário') and adds ordering and scope details. It explicitly names sibling tools (budget_comparison, categories_insights) and contrasts their purposes, so an agent can distinguish list_budgets from nearby alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear when-to-use guidance: list_budgets is for listing budgeted values, budget_comparison is for comparing a specific budget against actual spending, and categories_insights handles cross-category comparison without a Budget. This explicit routing removes ambiguity about which tool to select.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All CDF Finance toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation3/5

The tools are individually well-described and many cross-reference their closest neighbors, but the set contains several easily confused clusters: create_transaction/confirm_new_transaction, update_equity/add_equity_valuation, the invoice tools (current_invoice, next_invoice, list_pending_invoices, get_invoice), and the many analytics/projection tools. The descriptions help a careful reader, but with 81 tools an agent is likely to misselect among these overlapping surfaces.

Naming Consistency3/5

CRUD operations consistently use create_/list_/update_/delete_ plus a resource noun, and all names are snake_case. However, there is a large second group of noun-phrase analytics tools (cashflow_forecast, spending_projection, categories_insights, transport_routine) plus one-off verbs such as can_afford, pay_invoice, and validate_current_invoices, so the naming convention is mixed even though it remains readable.

Tool Count1/5

81 tools is far beyond the practical MCP tool surface and exceeds the rubric's 50+ extreme-mismatch threshold. Even if each tool maps to a real finance endpoint, the volume overwhelms an agent's context window and makes selection much harder.

Completeness4/5

The server covers the finance lifecycle extensively: accounts, cards, invoices, transactions, recurring rules, budgets, goals, debts, equities, categories, tags, cost centers, profile, projections, and insights all have working read/write paths. Minor gaps remain, such as no update/delete for tags and no direct update/delete for system-generated invoices, but agents can usually work around these.

Resources