CDF Finance

Criar tag

create_tag

Cria uma nova tag para marcar transações do usuário autenticado. Não valida duplicidade de nome.

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_tag"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Nome da tag
`color`	No	Cor da tag (ex: hex '#RRGGBB')

Output Schema

Name	Required	Description	Default
`id`	No
`name`	No
`color`	No
`userId`	No
`createdAt`	No
`updatedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 1, 2026
- addedInput schema / properties / color / description
```
Added value: +"Cor da tag (ex: hex '#RRGGBB')"
```
- addedInput schema / properties / name / description
```
Added value: +"Nome da tag"
```
First observedSep 1, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already mark this as non-read-only, non-idempotent, and non-destructive. The description adds a non-obvious behavioral caveat: 'Não valida duplicidade de nome', which tells the agent duplicate names are allowed and not rejected. It also scopes the operation to the authenticated user's transactions.

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 short sentences in Portuguese, front-loaded with the action and followed by the one caveat that matters. No filler or redundancy.

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 simple two-parameter creation tool with output schema and safety annotations, the description covers the essential behavior. It could additionally direct the agent to list existing tags when uniqueness matters, but that is a usage-guidance enhancement rather than a blocker.

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?

With 100% schema coverage, the schema already documents both parameters. The description adds one meaningful parameter-related fact: the `name` field is not validated for duplicate, so the agent should not assume uniqueness. This goes beyond the schema's plain type/description.

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 and resource: 'Cria uma nova tag para marcar transações do usuário autenticado.' It clearly identifies what is created and for whom, and the resource 'tag' distinguishes it from sibling tools like create_category and create_transaction.

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?

No guidance on when to prefer this tool over alternatives is given. It does not mention checking existing tags with list_tags before creating, nor any condition that would rule this tool out. The duplicate-name warning is behavioral, not usage routing.

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.