Skip to main content
Glama

merge_payees

Destructive

Merge a source Payee into a target Payee. Transactions and aliases move to the target; the target wins silently on defaultCategoryId conflict; the source is deleted. Use to dedupe near-duplicates like "Amazon" and "AMZN MKT". 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": {
      "sourceId": "<sourceId>",
      "targetId": "<targetId>"
    },
    "name": "merge_payees"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceIdYesPayee id to merge from (will be deleted).
targetIdYesPayee id to merge into (kept).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Adds substantial behavior beyond the destructiveHint annotation: transactions and aliases are re-parented, the target silently wins on defaultCategoryId conflict, and the source is deleted. It also names the required finance:delete scope, which annotations cannot convey.

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 dense sentences with no waste: operation first, merge side-effects second, usage example and prerequisite last. Every sentence carries distinct 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 destructive, two-parameter tool this covers what moves, what is destroyed, conflict precedence, and authorization requirements. Minor gaps remain: it does not say whether anything is returned or what happens on invalid/same ids, which matters slightly given there is no output schema.

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 both parameters already carry descriptions stating which id is deleted and which is kept. The description's conflict-resolution note is behavioral rather than parameter-level, so it adds little meaning beyond the schema; baseline 3 applies.

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 ("Merge a source Payee into a target Payee") and immediately scopes it with a concrete use case (dedupe near-duplicates like "Amazon" and "AMZN MKT"), which distinguishes it from sibling delete_payee and bulk_delete_payees.

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 when-to-use signal via the dedupe example, and the requirement of finance:delete scope clarifies prerequisites. It does not explicitly name alternatives or say when not to use it (e.g., use delete_payee to remove a payee without merging), leaving that to inference.

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.