CDF Finance

Criar centro de custo

create_cost_center

Cria um centro de custo novo (não-padrão — isDefault sempre começa false).

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": {
      "name": "<name>"
    },
    "name": "create_cost_center"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Nome do centro de custo
`description`	No	Descrição livre do centro de custo

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.

Changed1 schema field changedSep 1, 2026
- addedInput schema / properties / name / description
```
Added value: +"Nome do centro de custo"
```

Changed3 schema fields changedSep 1, 2026

removedInput schema / properties / color

Removed value: -{
-  "type": "string"
-}

addedInput schema / properties / description

Added value: +{
+  "description": "Descrição livre do centro de custo",
+  "type": "string"
+}

removedInput schema / properties / icon

Removed value: -{
-  "type": "string"
-}

First observedSep 1, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already signal that this is a mutating, non-idempotent, non-destructive operation. The description adds meaningful behavioral context beyond those annotations by guaranteeing that a newly created cost center always has `isDefault` set to false, which an agent could not infer from the schema alone.

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?

A single, clear sentence that states the action, the object, and the most important behavioral nuance with no wasted words. The key behavior is front-loaded and easy to parse.

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?

This is a simple creation tool with only two parameters, one required, full schema descriptions, and an output schema present. The description plus annotations and schema cover all essential information an agent needs to call it correctly.

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%, and both `name` and `description` are already described in the schema. The description does not add further parameter-level semantics, but it does not need to because the schema already carries the burden.

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 uses a specific verb ('Cria') and resource ('centro de custo novo'), and adds the key distinguishing trait that created cost centers are non-default with `isDefault` starting false. This clearly separates it from update, delete, and list siblings.

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?

The use case is implied by the verb and the word 'novo': create a new cost center rather than updating or deleting an existing one. However, the description does not explicitly state when to prefer this over update_cost_center or mention any prerequisites, so guidance remains implicit.

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.