Zen Money MCP

delete_budget

Remove a category budget for a specific month by clearing its fixed status and resetting the amount to zero. Use it to undo monthly budget limits or correct outdated category planning.

Instructions

Убрать бюджет категории за месяц, сняв фиксацию и обнулив сумму.

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": {
      "month": "<month>",
      "type": "<type>"
    },
    "name": "delete_budget"
  }
}

Input Schema

Name	Required	Description	Default
`type`	Yes
`month`	Yes
`category`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 1, 2026

TDQS

B3/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does add real value by disclosing that this is not a hard delete: it removes the fixation and zeroes the amount. It omits reversibility, required permissions, and what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single economical sentence that leads with the action and its effect; nothing is padded, though the brevity is partly why parameter coverage is thin.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter mutation with no annotations, no output schema and no schema descriptions, the description explains the mutation effect but leaves the required 'type' argument, the month format, and error/edge behavior unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate. It vaguely covers 'month' (за месяц) and 'category' (бюджет категории) but says nothing about the required 'type' enum (income/outcome) or the YYYY-MM format, leaving a required parameter undocumented.

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?

States a specific verb (remove) and resource (category budget for a month), so it is distinguishable from set_budget and list_budgets. It does not name those siblings explicitly, and it underplays the required 'type' dimension, so it falls short of a 5.

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 indication of when to use this versus set_budget (e.g., to clear a value rather than change it), no prerequisites, and no note on whether the category argument is optional or what happens when it is omitted. Usage must be inferred entirely.

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