CDF Finance

Atualizar dívida

update_debt

Idempotent

Atualiza uma dívida (parcial — campo omitido ou string vazia mantém o atual; status/category/creditor/description/currency seguem essa mesma regra, não há como limpar um valor já preenchido por esta tool). equityId, se enviado, é revalidado contra o dono. Efeito colateral: recalcula analytics e insights do usuário.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Id da dívida (Debt) a atualizar
`name`	No
`status`	No
`dueDate`	No
`category`	No
`creditor`	No
`currency`	No
`equityId`	No	Novo Equity vinculado; precisa pertencer ao usuário
`description`	No
`totalAmount`	No
`interestRate`	No	Taxa de juros mensal em %
`remainingAmount`	No	Novo saldo devedor — use para registrar um pagamento parcial

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	No

Schema Changelog

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

Changed11 schema fields changedSep 1, 2026

addedInput schema / properties / category
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / creditor
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / currency
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / description
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / equityId

Added value: +{
+  "description": "Novo Equity vinculado; precisa pertencer ao usuário",
+  "type": "string"
+}

addedInput schema / properties / id / description

Added value: +"Id da dívida (Debt) a atualizar"

addedInput schema / properties / interestRate / description
```
Added value: +"Taxa de juros mensal em %"
```
addedInput schema / properties / name
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / remainingAmount / description

Added value: +"Novo saldo devedor — use para registrar um pagamento parcial"

addedInput schema / properties / status

Added value: +{
+  "enum": [
+    "ACTIVE",
+    "PAID",
+    "OVERDUE"
+  ],
+  "type": "string"
+}

addedInput schema / properties / totalAmount
```
Added value: +{
+  "type": "number"
+}
```

First observedSep 1, 2026

TDQS

A4.4/5.0

Behavior5/5

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

It discloses that the update is partial, that omitted fields and empty strings keep the current value, that certain string fields cannot be cleared, and that equityId is revalidated against the owner. It also warns that analytics and insights are recalculated, which is clearly beyond the hints provided by annotations.

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?

The description is dense but efficient: three sentences front-load the action, then cover partial-update behavior and side effects. No filler; every sentence carries essential information.

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 12-parameter mutation tool, the description provides the essential call semantics: partial merge, no clearing, owner validation, and side effects. With the output schema present and annotations covering mutation/idempotence, this is nearly complete; it only lacks explicit alternative routing and a few parameter-format details.

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 coverage is only 33%, but the description compensates with a general partial-update rule that applies semantics to omitted/empty parameters, names several affected fields, and adds owner validation for equityId. Specific formats such as dueDate and the relationship between totalAmount and remainingAmount remain undocumented, so it is strong but not complete.

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 'Atualiza uma dívida' — a specific verb plus resource — and then refines it as a partial update. This clearly distinguishes it from sibling tools such as create_debt, delete_debt, and list_debts.

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

Usage Guidelines3/5

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

There is no explicit when-to-use or alternative routing; the operative guidance is only the implied meaning 'use this to modify an existing debt'. No exclusions or conditions are given to steer an agent away from create/delete/list siblings.

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

All CDF Finance tools Inspect

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.

Atualizar dívida

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources