Skip to main content
Glama
Sign In

McpStamp Bank Statements

by io.github.theluckystrike
OverviewDiscussionsAdmin

Search transactions

transactions_search
Read-onlyIdempotent

Find transactions whose description, counterparty, category or account contains the query. Case-insensitive substring search, never a regex, so a query with brackets in it cannot hang the server.

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

Input Schema

NameRequiredDescriptionDefault
toNoISO date, inclusive
fromNoISO date, inclusive
limitNoRows returned, default 100
queryYesText to look for, e.g. "spotify" or "acme"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnlyHint and idempotentHint annotations, the description adds materially useful behavioral detail: case-insensitive substring matching, literal (non-regex) matching, and the safety consequence that bracket-containing queries cannot hang the server. This shapes how an agent should construct queries and calibrates expectations.

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 entire description is a single front-loaded sentence that states the core behavior first and then adds a precise, relevant caveat about regex behavior. Every part earns its place; there is no filler or repetition of schema content.

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

Completeness4/5

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

With annotations covering the safety profile and schema covering all parameters, the description is sufficient for an agent to invoke this simple search tool correctly. It does not describe the return shape or ordering, but the tool's behavior is straightforward and the lack of an output schema lowers the burden.

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 description coverage is 100%, so the baseline is 3. The description adds value by clarifying that the query parameter is matched as a case-insensitive substring against four specific fields, which the schema does not state. It does not add anything about to/from or limit, but those are already adequately documented in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Find') and resource ('transactions'), and explicitly enumerates the searchable fields: description, counterparty, category, or account. It clearly communicates the tool's purpose, though it does not explicitly name sibling tools to differentiate from them.

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 this is the right tool when you need to locate transactions by text contained in certain fields, but it gives no explicit guidance about when not to use it or how it compares to transactions_list or statement_summary. The 'never a regex' note is a behavior constraint, not usage guidance.

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

All McpStamp Bank Statements toolsInspect
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