PocketLedger MCP

Search transactions

search_transactions

Read-onlyIdempotent

Search a user's saved expense transactions by date range, category, merchant, keyword, currency, deleted status, and limit. Do not use for investment advice, income creation, bank credential storage, or calendar tasks.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_transactions"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`cursor`	No
`period`	No	Preset reporting period. Use 'custom' only together with date_from and date_to.
`date_to`	No
`keyword`	No
`category`	No	Expense category name selected from list_categories when possible.
`currency`	No	ISO 4217 currency code, e.g. USD, EUR, GBP.
`merchant`	No	Merchant or payee name in plain text, preferably in English when the user asks to save in English.
`timezone`	No	IANA timezone used to interpret dates and relative words like today or yesterday, e.g. 'UTC'.
`date_from`	No
`include_deleted`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 4, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, so the description adds no behavioral context beyond listing filter types. No contradiction.

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 sentences, no redundancy, but the second sentence about prohibited uses feels slightly misplaced for this tool's core function.

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?

For a tool with 11 parameters, pagination (cursor) is not mentioned in the description, though an output schema exists. The description is adequate for basic understanding but misses key context.

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 only 45%, and the main description merely lists filter categories without adding syntax, format, or parameter-specific details. Parameters like cursor, date_from, and include_deleted lack schema descriptions and are not elaborated.

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 'Search a user's saved expense transactions' with specific filter parameters, distinguishing it from sibling tools like delete_transaction, log_transaction, etc.

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 includes a negative directive ('Do not use for investment advice...'), but does not provide positive guidance on when to use this tool versus alternatives like get_summary or get_report.

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

All PocketLedger MCP 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?