Skip to main content
Glama
Sign In

CDF Finance

by io.github.VessellTech
OverviewDiscussionsAdmin

Excluir orçamento

delete_budget
DestructiveIdempotent

Exclui um orçamento. Efeito colateral: recalcula analytics e insights do usuário. Não apaga nem desvincula as transações que eram comparadas contra ele.

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": "delete_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId do orçamento (Budget) a excluir

Output Schema

NameRequiredDescriptionDefault
countNo
successNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / id / description
      Added value: +"Id do orçamento (Budget) a excluir"
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true), the description discloses two important behavioral details: it recalculates user analytics and insights, and it does not delete or unlink transactions compared against the budget. This adds meaningful context about side effects and non-effects, which is exactly what an agent needs.

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 two short sentences, front-loading the primary action and immediately following with the most critical side effects. Every sentence adds value and there is no redundant wording.

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 tool with a single documented parameter, output schema present, and annotations covering safety and idempotency, the description covers the remaining behavioral context (side effects and what is not affected). Nothing essential is missing for an agent to invoke 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 the single parameter 'id' is fully described in the schema as the budget ID to delete. The description adds no additional parameter-level meaning, so baseline 3 is appropriate.

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 ('Exclui') and resource ('orçamento'), clearly identifying what the tool deletes. It implicitly differentiates from sibling tools like create_budget, update_budget, and list_budgets by stating the delete operation on the exact resource.

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 usage context is implied: use this when you need to delete a budget. However, the description does not explicitly state when to use this tool over alternatives, nor does it mention any exclusions or prerequisites. It provides no direct routing guidance among the budget-related sibling tools.

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
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.

Resources