PocketSmith

delete_transaction

DestructiveIdempotent

Permanently deletes a transaction by its ID. This is irreversible. Use list_transactions to find transaction IDs. Requires confirmation across two turns: call once without confirm to get a preview of what will be deleted, show the preview to the user, and wait for their reply. Only pass confirm: true after the user approves the previewed deletion in a later message - the user's original deletion request does not count as approval.

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

Input Schema

Name	Required	Description	Default
`id`	Yes	The unique identifier of the transaction to delete.
`confirm`	No	Must be true to actually delete. Only set true after the user has seen the preview from a prior call and explicitly approved it in a subsequent message. Never true on the first call, even when the user's request sounds certain. Omit (or pass false) to get a preview of what will be deleted without deleting anything.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 31, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds critical context beyond them: the deletion is irreversible, the first call without confirm returns a preview, and deletion is gated on explicit user approval in a later message.

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?

Front-loaded with the irreversible action, then the ID-lookup pointer, then the confirmation protocol. Four sentences, each carrying distinct operational information with no filler.

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 two-parameter tool with no output schema, the description covers everything an agent needs: how to find the ID, what the first call returns, and the exact condition for the destructive call.

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 coverage is 100% and the confirm parameter is already well documented, so the schema does most of the work. The description still adds value by stating the lifecycle of the confirm flag across turns and clarifying that the original request is not approval, but it mostly reinforces rather than extends the schema text.

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 ('Permanently deletes a transaction by its ID') plus the irreversibility qualifier, which immediately distinguishes it from update_transaction and the other delete_* siblings that target different resources.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly routes the agent to list_transactions to obtain IDs and spells out the two-turn confirmation protocol, including the non-obvious exclusion that the user's original deletion request does not count as approval.

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

All PocketSmith tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?