Skip to main content
Glama
cashcast-mcp

cashcast-mcp

Transactions

get_records
Read-onlyIdempotent

Retrieve individual transaction rows to drill into a reported figure—not totals. Filter by date, account, category, amount, or counterparty; transfers excluded by default.

Instructions

Individual transactions, for drilling into a figure another tool reported. Returns ROWS AND NO TOTALS by design. Transfers between the user's own accounts are excluded unless include_transfers is set, and are labelled isTransfer when included.

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

Input Schema

NameRequiredDescriptionDefault
toNoInclusive end date.
fromNoInclusive start date.
limitNo
accountNoAccount id.
categoryNoExact category name, case-insensitive.
include_transfersNoNever fold an included transfer into a total.
min_abs_amount_eurNoOnly transactions at least this large in absolute EUR.
counterparty_containsNoCase-insensitive substring of the counterparty.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description isn't needed for that. It does add real behavioral context: results are row-level with no totals, own-account transfers are excluded by default and flagged via isTransfer when included, which prevents double-counting mistakes. It says nothing about pagination or what the limit default implies for result-completeness.

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?

Three short sentences, no filler, and the most decision-relevant fact (rows, not totals) is emphasized up front in caps. Every sentence carries a distinct constraint.

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 8 optional parameters, 88% schema coverage and rich annotations, the definition covers output shape and the transfer gotcha, which is the main thing an agent could get wrong. It is slightly thin on result-volume behavior (limit default 100, max 500) and on how filters combine.

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 88%, so the baseline is 3; the description earns a bump by explaining the practical effect of include_transfers (excluded unless set, then labelled isTransfer) rather than just restating the flag. That meaning goes beyond the schema's 'Never fold an included transfer into a total' wording.

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?

Opens with a specific resource ('Individual transactions') and a stated purpose ('for drilling into a figure another tool reported') that functionally separates it from the aggregate siblings like get_spending or get_overview. It does not name a sibling explicitly, but 'ROWS AND NO TOTALS by design' makes the distinction unmistakable.

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

Usage Guidelines4/5

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

The clause 'for drilling into a figure another tool reported' is clear when-to-use guidance: this is the detail tool after an aggregate. It offers no explicit when-not or named alternative (e.g., 'use get_spending for totals'), so it stops short of full routing guidance.

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