Pocketsmith MCP Server

Overview Schema Source Related Servers Discussions Admin

pocketsmith_search_transactions

Search personal finance transactions by payee, category, or notes to find specific spending. Exclude transfers, zero-amount entries, or unwanted categories for targeted results.

Instructions

Search transactions by keyword (payee, category, notes). Transfers excluded by default.

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": {
      "query": "<query>"
    },
    "name": "pocketsmith_search_transactions"
  }
}

Input Schema

Name	Required	Description
`query`	Yes	Search query to match against transaction fields
`limit`	No	Maximum number of transactions to return (default 50)
`exclude_transfers`	No	Exclude transfer transactions (default true)
`exclude_zero`	No	Exclude zero-amount transactions (default true)
`exclude_category_ids`	No	Category IDs to exclude from results

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedMay 2, 2026

addedInput schema / properties / exclude_category_ids

Added value: +{
+  "description": "Category IDs to exclude from results",
+  "items": {
+    "type": "integer"
+  },
+  "type": "array"
+}

addedInput schema / properties / exclude_transfers

Added value: +{
+  "description": "Exclude transfer transactions (default true)",
+  "type": "boolean"
+}

addedInput schema / properties / exclude_zero

Added value: +{
+  "description": "Exclude zero-amount transactions (default true)",
+  "type": "boolean"
+}

First observedv0.1.0Feb 17, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description must cover behavioral traits. It mentions default exclusions but lacks details on pagination, read-only nature, search semantics (case sensitivity, fuzzy matching), or rate limits.

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?

Two concise sentences, front-loaded with purpose. Every word adds value without redundancy.

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

Completeness3/5

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

With 5 parameters, no output schema, and no annotations, the description covers search scope and defaults but omits return format, pagination details, and search behavior nuances (e.g., case sensitivity). Adequate but not thorough.

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% with good parameter descriptions. The tool description adds context by specifying which fields are searched (payee, category, notes) and default behavior for exclusions, enhancing understanding 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 clearly states the tool searches transactions by keyword across specific fields (payee, category, notes) and notes default exclusion of transfers, distinguishing it from list-only or mutation tools.

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

Usage Guidelines3/5

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

The description implies usage (searching) but does not explicitly state when to use vs. alternatives like pocketsmith_list_transactions, nor does it mention when transfers are excluded or how to include them.

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