Skip to main content
Glama

CDF Finance

by io.github.VessellTech

Atualizar orçamento

update_budget
Idempotent

Atualiza um orçamento (parcial — campos omitidos ou string vazia mantêm o valor atual). Efeito colateral: recalcula analytics e insights do usuário, igual create_budget. Devolve apenas { count }, não o orçamento atualizado.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesId do orçamento (Budget) a atualizar
nameNo
typeNo
yearNo
monthNo
amountNo
periodNo
categoryNo'ALL' para remover o filtro de categoria
currencyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo

Schema Changelog

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

  1. Changed8 schema fields changed
    • addedInput schema / properties / category
      Added value: +{
+  "description": "'ALL' para remover o filtro de categoria",
+  "type": "string"
+}
    • addedInput schema / properties / currency
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / id / description
      Added value: +"Id do orçamento (Budget) a atualizar"
    • addedInput schema / properties / month
      Added value: +{
+  "type": "integer"
+}
    • addedInput schema / properties / name
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / period
      Added value: +{
+  "enum": [
+    "MONTHLY",
+    "YEARLY"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / type
      Added value: +{
+  "enum": [
+    "INCOME",
+    "EXPENSE",
+    "INVESTMENT"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / year
      Added value: +{
+  "type": "integer"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The description discloses meaningful behavioral details beyond the annotations: partial updates preserve omitted fields, analytics and insights are recalculated, and the response only contains `{ count }`. This goes well beyond what readOnlyHint, idempotentHint, and destructiveHint already convey.

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 concise sentences carry substantial information: purpose, partial-update behavior, side effect, and return shape. Everything earns its place, and the most important behavioral detail is front-loaded.

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

Completeness4/5

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

For a 9-parameter mutation tool with annotations and an output schema, the description covers the essential decisions: what is updated, how omission behaves, what side effects occur, and what is returned. Remaining gaps such as authentication or validation are not critical here.

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

Parameters4/5

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

Schema description coverage is low at 22%, but the description compensates with a key global parameter rule: omitted fields or empty strings keep the current value. This is critical for correctly using the optional parameters, even though individual field semantics are not elaborated.

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 clearly states 'Atualiza um orçamento', identifying the specific action and resource. It also adds important scope with 'parcial' and explicitly references create_budget, helping disambiguate update from create operations.

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

Usage Guidelines4/5

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

The description gives clear usage context by explaining partial update behavior and the side effect compared to create_budget. It does not explicitly list when not to use the tool, but the context is strong enough for an agent to select it appropriately.

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