Pocketsmith MCP Server

Overview Schema Source Related Servers Discussions Admin

pocketsmith_get_transaction

Retrieve detailed information about a specific transaction using its unique ID. Enables querying transaction data from your Pocketsmith account for review or analysis.

Instructions

Get details of a specific 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_get_transaction"
  }
}

Input Schema

Name	Required	Description	Default
`transaction_id`	Yes	The transaction ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Feb 17, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations exist, so the description must carry the full burden. It only states 'Get details' (a read operation) but omits any behavioral traits such as rate limits, authentication requirements, error handling (e.g., behavior for invalid/missing ID), or what 'details' precisely includes.

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?

The description is a single short sentence with no extraneous words. It is concise but could slightly expand on the output format without becoming verbose.

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?

With no output schema, the description should indicate what 'details' are returned (e.g., full transaction object, specific fields). It lacks this information, making the tool incomplete for an agent to understand the return structure.

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 the parameter description is minimal ('The transaction ID'). The tool description adds no additional meaning beyond the schema, meeting the baseline of 3.

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 clearly states the action ('Get details') and the target resource ('a specific transaction by ID'). It effectively distinguishes this tool from siblings like 'pocketsmith_list_transactions' and 'pocketsmith_search_transactions' by specifying retrieval by individual ID.

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 guidance is provided on when to use this tool versus alternatives such as listing or searching. It implicitly assumes the agent already has a transaction ID but does not explain the prerequisite or contrast with bulk operations.

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