Skip to main content
Glama

Delete budget category

delete-budget-category
Destructive

Deletes a budget category and its planned amount. Its expenses stay in the budget, without a category. Confirm with the user 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": {
      "id": "<id>"
    },
    "name": "delete-budget-category"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe category, from get-budget.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, so the safety profile is known; the description goes further and discloses the exact cascade outcome — planned amount removed, expenses retained as uncategorized. That is precisely the consequence an agent needs before triggering an irreversible delete, and it is not derivable from the annotations or schema.

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?

Three short sentences, no filler: action, consequence, precondition. Front-loads the effect and puts the confirmation instruction last where it gates the call.

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 single-parameter destructive tool with no output schema and full annotation coverage, nothing material is missing: what is deleted, what survives, and the confirmation requirement are all stated.

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% and the id property already documents 'The category, from get-budget.', so the description adds no meaning beyond it. Baseline 3 applies since the schema carries full parameter 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?

States a specific verb and resource ('Deletes a budget category') and immediately scopes what that means: the planned amount goes, the expenses do not. That second sentence also separates it from delete-expense, which is the sibling an agent could otherwise confuse it with.

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

Usage Guidelines4/5

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

Gives a clear precondition ('Confirm with the user first') that tells the agent this is a gate-before-call operation. It does not name an alternative such as update-budget-category for cases where the category should merely be changed rather than removed, so routing guidance is implicit rather than explicit.

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.

Resources