CDF Finance

Atualizar centro de custo

update_cost_center

Idempotent

Atualiza nome/descrição de um centro de custo (parcial — campo omitido/vazio mantém o valor atual).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "update_cost_center"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	ID do centro de custo a atualizar
`name`	No	Novo nome do centro de custo
`description`	No	Nova descrição livre

Output Schema

Name	Required	Description	Default
`id`	No
`name`	No
`userId`	No
`createdAt`	No
`isDefault`	No
`updatedAt`	No
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 1, 2026
- addedInput schema / properties / description / description
```
Added value: +"Nova descrição livre"
```
- addedInput schema / properties / name / description
```
Added value: +"Novo nome do centro de custo"
```
Changed4 schema fields changedSep 1, 2026
- removedInput schema / properties / color
```
Removed value: -{
-  "type": "string"
-}
```
- addedInput schema / properties / description
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / icon
```
Removed value: -{
-  "type": "string"
-}
```
- addedInput schema / properties / id / description
```
Added value: +"ID do centro de custo a atualizar"
```
First observedSep 1, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The description discloses a non-obvious behavior beyond the annotations: omitted or empty fields preserve the current value, which is critical for a partial update call. It is consistent with readOnlyHint=false and idempotentHint=true; it does not go into side effects or permissions, but the annotations lower that burden.

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?

One compact sentence with a parenthetical qualifier; every phrase adds value and no schema information is repeated unnecessarily. The key update scope 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 three-parameter update tool, the description, complete input schema, idempotentHint annotation, and output schema together supply enough to invoke it correctly without further documentation. The partial-update nuance is explicitly included.

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 100%, so the baseline is satisfied. The description adds parameter-level meaning by clarifying that name/description can be partially supplied and that omitting or sending an empty string keeps existing values, which the schema itself does not state.

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 identifies a specific action ('Atualiza'), a precise resource ('centro de custo'), and the affected fields ('nome/descrição'). This distinguishes it from create_cost_center, delete_cost_center, list_cost_centers, and the other update_* siblings without ambiguity.

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

Usage Guidelines2/5

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

There is no explicit guidance about when to use this tool versus alternatives such as create_cost_center for a new center or delete_cost_center for removal. The reader must infer the update use case from the verb; the partial-update note is operational behavior, not usage-selection guidance.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.