Skip to main content
Glama

List recurring expenses

crunch_list_recurring_expenses
Read-only

List recurring expenses such as rent, phone or software subscriptions, returning supplier, amount, status and next date so you can review regular bills. Filter, sort and page results as needed.

Instructions

List recurring expenses (regular bills such as rent, phone or software subscriptions that Crunch creates automatically) with supplier, amount, status and next date.

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

Input Schema

NameRequiredDescriptionDefault
allNoFetch every page (up to max_items) instead of a single page
rawNoReturn the full objects from the API instead of compact summaries (larger)
pageNoPage to fetch, starting at 0 (default 0)
sizeNoResults per page, up to 200 (default 50)
sortNoSort order as field,asc or field,desc, for example postingDate,desc
limitNoMaximum number of items
fieldsNoKeep only these fields (dot paths, such as supplier.companyName)
searchNoCase-insensitive substring match on any value
max_itemsNoWith all=true, stop after this many results (default 1000, at most 10000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine context by explaining that Crunch creates these records automatically, which tells the agent the data is system-generated configuration rather than user-entered transactions. It says nothing about pagination defaults or result shape, though the schema covers paging parameters.

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?

A single front-loaded sentence that names the resource first, then clarifies it, then lists returned fields. No redundant restatement of the title and nothing that could be trimmed without losing information.

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?

For a read-only list tool whose nine parameters are fully described in the schema and whose safety profile is carried by annotations, the description covers purpose and data shape adequately. Slightly short of complete because it does not route the agent between this tool and the closely named crunch_list_expenses or the non-paged get variant.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all nine parameters (all, raw, page, size, sort, limit, fields, search, max_items) are already documented in the input schema. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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?

States a specific verb (List) and resource (recurring expenses), and parenthetically defines what a recurring expense is — regular bills like rent, phone or software subscriptions that Crunch creates automatically — plus the fields returned (supplier, amount, status, next date). It implicitly separates itself from crunch_list_expenses by emphasizing the automatic recurring nature, but never names the non-recurring sibling, so differentiation is left partly to inference.

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: an agent can infer this is for viewing configured recurring bills rather than actual booked expenses. There is no explicit when-to-use/when-not statement, no pointer to crunch_list_expenses for real expenses or crunch_get_recurring_expense for a single item, and no mention of prerequisites such as authentication.

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

Deploy Server

Other Tools