Skip to main content
Glama
Sign In
Pocketsmith MCP Server

Pocketsmith MCP Server

by dannyshaw
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

pocketsmith_delete_transaction

Remove a transaction from Pocketsmith by providing its ID. Clean up accounts by deleting incorrect or duplicate transactions to maintain accurate financial records.

Instructions

Delete a transaction by ID

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": "pocketsmith_delete_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
transaction_idYesThe transaction ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description is the sole source of behavioral information. It states the action is deletion, implying mutation and destruction, but does not disclose potential consequences (e.g., irreversibility, cascading effects) or required authentication/authorization context.

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?

The description is a single, concise sentence with no extraneous information, making it highly efficient for an agent to process.

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 mutation tool with no output schema and no annotations, the description is insufficient. It does not mention return values (e.g., success indicator, deleted object), error conditions (e.g., transaction not found), or any post-deletion state, leaving the agent with incomplete context.

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%, with the parameter description already explaining its role. The description adds 'by ID' which reinforces the parameter's function but does not provide additional meaning beyond the schema.

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 'Delete a transaction by ID' clearly states the verb (delete), resource (transaction), and identification method (by ID). It effectively distinguishes from sibling tools like create, update, or categorize.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not specify prerequisites, such as transaction existence or user permissions, nor does it mention any context where deletion is appropriate.

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

Deploy Server

Other Tools