Skip to main content
Glama

delete_payee

Destructive

Delete a Payee. Linked transactions retain their categoryId but their payeeId is set to null. Use cautiously — this is irreversible. Requires finance:delete scope.

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_payee"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPayee id to delete.
ignoreFutureNotrue also adds the payee names to the ignore list, so imports never recreate it. Default false

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / ignoreFuture
      Added value: +{
      +  "description": "true also adds the payee names to the ignore list, so imports never recreate it. Default false",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

The annotations already declare destructiveHint=true, but the description goes well beyond them: it discloses the exact downstream effect on linked transactions (categoryId retained, payeeId nulled), states irreversibility, and names the required finance:delete scope. These are precisely the operational facts an agent cannot obtain from structured fields.

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?

Four short sentences, front-loaded with the action, then the side effect, then the risk warning, then the auth requirement. No sentence is redundant and nothing important is buried.

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 two-parameter destructive tool with no output schema, everything an agent needs is present: the effect on related records, irreversibility, and the permission scope. There is no meaningful gap left to fill.

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 description coverage is 100%, including a detailed explanation of ignoreFuture and its import-blocking effect, so the schema already carries parameter meaning. The description adds nothing parameter-specific, which makes the baseline 3 appropriate.

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 a Payee") in the first sentence, which cleanly separates it from singular-vs-bulk siblings like bulk_delete_payees and from merge_payees. An agent knows immediately what this call does.

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 gives a real caution ("Use cautiously — this is irreversible"), which is useful guidance about when to think twice, but it never names an alternative such as bulk_delete_payees for multiple ids or merge_payees when consolidation is the real intent. Usage is implied rather than routed.

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.