Skip to main content
Glama
moneywiz-mcp

moneywiz-mcp

by kyledh

moneywiz_delete_transaction

DestructiveIdempotent

Deletes a specified MoneyWiz transaction; for transfers, it removes both linked legs to keep the ledger consistent.

Instructions

Delete a transaction. Both legs go for a transfer.

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": {
      "transaction_id": "<transaction_id>"
    },
    "name": "moneywiz_delete_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
transaction_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false. The description adds one genuinely useful behavioral fact beyond them: that a transfer's paired leg is also deleted, which an agent could not infer from the schema. It says nothing about whether the delete is permanent, what happens to reconciled balances, or what occurs if the ID doesn't exist.

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?

Two short sentences, front-loaded with the core action and no filler. The brevity is appropriate, though the second sentence's phrasing 'Both legs go for a transfer' is slightly awkward and could be clearer.

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

Completeness2/5

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

For a destructive, cascading delete with no output schema and no documented parameter, the definition is thin. An agent is left unsure whether the operation is permanent, how to identify the target transaction uniquely, or how to confirm success beyond an error-free response.

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 description coverage is 0% for the single transaction_id parameter, so the description should compensate and does not. It never states whether transaction_id is a UUID, integer string, or which leg of a transfer should be supplied — the latter is especially relevant given the cascade behavior it does describe.

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 and resource: 'Delete a transaction.' The second sentence adds concrete scope that the name alone would not convey, namely that transfer deletions cascade to both legs. It does not explicitly distinguish itself from siblings like moneywiz_set_transaction_status, but the operation 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance. There is no mention of alternatives such as voiding or archiving a transaction via moneywiz_set_transaction_status, nor any note about prerequisites or when deletion is appropriate.

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