Skip to main content
Glama

Update budget category

update-budget-category
DestructiveIdempotent

Sets the amount the couple plans to spend on a budget category, or renames it. Only the fields you pass change; an empty planned_amount or 0 clears it. Category ids come from get-budget.

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": "update-budget-category"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe category, from get-budget.
nameNo
planned_amountNoIn euro, e.g. "3000"; empty to clear.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations cover the safety profile (destructiveHint=true, idempotentHint=true, readOnlyHint=false), and the description adds context beyond them: partial-update semantics (only fields you pass change) and the clearing rule (empty planned_amount or 0 clears it), which explains what the destructive hint actually means here. It does not cover permissions or what happens to a rename that collides with an existing name.

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, front-loaded with the primary action, then the update semantics and the id source. No filler and every clause carries information.

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 three-parameter patch tool with no output schema, it covers the action, partial-update behavior, clearing semantics, and where ids come from. Remaining gaps (rename collisions, error outcomes, auth) are minor for this complexity level.

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?

Schema coverage is 67%, and the description compensates where the schema is thin: it clarifies that planned_amount can be cleared with 0 as well as an empty string, and that name performs a rename. The name parameter carries no schema description, but the description's mention of renaming covers its meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb+resource: it sets the planned amount for a budget category or renames it, and states the category scope, which separates it from update-budget and add/delete-budget-category. It never explicitly contrasts those siblings, but the resource is unambiguous.

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?

It tells the agent a prerequisite — category ids come from get-budget — which is genuinely useful routing information. It offers no when-not guidance, no mention of when to use add-budget-category versus this tool, and no note on behavior when an unknown id is passed.

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