Skip to main content
Glama

Cash Coach AI

List recurring payments

recurring_list
Read-onlyIdempotent

Read detected recurring series with recorded transaction IDs, first/last dates and separately labelled predictions. nextOffset identifies the next page of series. Linked transaction IDs identify actual past payments.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
activeOnlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare this a safe idempotent read, so the bar is lower, and the description still adds useful substance: what the records contain (recorded transaction IDs, first/last dates, 'separately labelled predictions') and how paging works. It stops short of describing page sizing or ordering, but no output schema exists so this is meaningful added context.

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?

Three short sentences, front-loaded with the resource and its contents, then pagination. The final sentence restates the transaction-ID point already made in the first, so there is minor redundancy but little true waste.

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 read-only list tool with annotations and no output schema, the description covers what comes back and how to page, which is most of what an agent needs. However, the activeOnly filter and the limit/offset bounds (limit capped at 25, offset at 5000) are undocumented, leaving real gaps.

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 coverage is 0% for three parameters, so the description carries the full burden, yet limit and activeOnly are never explained. Worse, it refers to 'nextOffset' while the schema exposes 'offset', which risks an agent mapping the wrong field; only the pagination concept is communicated, not the actual parameter.

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 states a specific verb+resource: reading 'detected recurring series' with first/last dates and predictions. This distinguishes it implicitly from transactions_list and spending tools, though it never names a sibling or explicitly contrasts the recurrence view with raw transactions.

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?

Usage is only implied by the phrase 'detected recurring series'; there is no statement of when to reach for this tool versus transactions_list or spending_snapshot. It also never explains when to set activeOnly, which is the one parameter that shapes which series come back.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources