Skip to main content
Glama

Delete cost budget

delete_cost_budget
Destructive

Delete one of the organisation's cost budgets; its card is no longer raised. Organisation admins only (billing.manage); audited with what it removed. Recreating it with set_cost_budget starts a new budget with a new id (read get_cost_budgets first).

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

Input Schema

NameRequiredDescriptionDefault
budget_idYesThe budget to delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the description earns credit only for going beyond that: it discloses the audit trail ("audited with what it removed") and the non-reversible identity semantics (a recreated budget gets a new id). Remaining gap is that it does not describe the response payload or failure modes, but with a destructive operation the safety and side-effect profile is well covered.

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 front-loaded sentence with the action and effect first, then permissions, then alternatives. Every clause carries distinct information: consequence, authorization, audit, and re-creation semantics. Nothing is redundant.

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 one-parameter destructive tool with no output schema and full annotation coverage, the description supplies everything an agent needs: the effect, the required role, the audit behavior, and how to handle the destroy/recreate cycle. No meaningful gap remains.

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 coverage is 100% for the single budget_id parameter, so the schema does the documentation work. The description adds only indirect guidance ("read get_cost_budgets first") on where the id comes from, which is useful but minimal; the baseline of 3 applies.

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?

States a specific verb and resource ("Delete one of the organisation's cost budgets") and immediately names the consequence ("its card is no longer raised"). It is clearly distinguishable from the sibling set_cost_budget (creation) and get_cost_budgets (read) that appear in the same sentence.

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

Usage Guidelines5/5

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

Explicitly gates usage with a permission requirement ("Organisation admins only (billing.manage)") and routes the agent: read get_cost_budgets first to obtain the id, and use set_cost_budget to recreate rather than attempting anything in-place. The alternative and the condition that selects it are both stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.