actual-budget-mcp

Overview Schema Source Related Servers Discussions Admin

delete_payee

Destructive

Delete a payee from your budget by first previewing, then confirming with the payee's exact name to make the irreversible change.

Instructions

Delete a payee. Destructive and irreversible: the first call only previews, and deleting requires confirm: true plus confirm_name set to the payee's exact name.

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": {
      "payee": "<payee>"
    },
    "name": "delete_payee"
  }
}

Input Schema

Name	Required	Description
`payee`	Yes	Payee name or ID to delete
`confirm`	No	Must be true to delete. Without it, the tool only previews.
`confirm_name`	No	The payee's exact name, echoed back as a safeguard.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.8.3Sep 8, 2026

addedInput schema / properties / confirm

Added value: +{
+  "description": "Must be true to delete. Without it, the tool only previews.",
+  "type": "boolean"
+}

addedInput schema / properties / confirm_name

Added value: +{
+  "description": "The payee's exact name, echoed back as a safeguard.",
+  "type": "string"
+}

First observedv0.6.1Jun 12, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations' destructiveHint and readOnlyHint, the description discloses that the operation is irreversible, that a first call only previews, and that confirmation requires an exact-name safeguard. This is substantive behavioral context an agent needs before invoking.

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 compact sentences with no filler. The core action is front-loaded, followed immediately by the critical safety requirements.

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 destructive three-parameter tool, the description fully covers how to invoke it safely: payee identification, preview behavior, and confirmation requirements. The lack of an output schema is not a significant gap here because the focus is on the destructive action and its guardrails.

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 description coverage is 100%, so the baseline is 3. The description adds value by sequencing the parameters into a safe workflow (preview first, then confirm with both confirm:true and confirm_name), which ties the parameter semantics together.

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 opens with a specific verb and resource: 'Delete a payee,' which is unambiguous and distinguishes this tool from sibling payee tools like create_payee and update_payee. The destructive/irreversible warning reinforces the operation's nature.

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?

It gives actionable usage context: the first call should preview, and actual deletion requires confirm:true plus the exact confirm_name. It does not explicitly name alternatives or say when not to use it, but the context makes the deletion workflow clear.

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