Skip to main content
Glama

Get recurring expense

crunch_get_recurring_expense
Read-only

Retrieves a recurring expense by ID, returning its template details—supplier, lines, and payment—plus its schedule for review or updates.

Instructions

Get a recurring expense in full: the template expense (supplier, lines, payment) and its schedule (recurringEvent).

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": {
      "recurring_expense_id": "<recurring_expense_id>"
    },
    "name": "crunch_get_recurring_expense"
  }
}

Input Schema

NameRequiredDescriptionDefault
recurring_expense_idYesRecurring expense ID (see crunch_list_recurring_expenses)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, openWorldHint=false), so the description's job is to explain what the payload contains, which it does by enumerating the template expense parts and the recurringEvent schedule. That is real value given there is no output schema. It stops short of noting any failure modes (e.g., what happens with a non-recurring or deleted ID), which the annotations do not cover either.

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?

One sentence, front-loaded with the action and immediately followed by the concrete contents of the response. Nothing is repeated from the title or annotations and no words are wasted.

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?

A read-only single-parameter getter with full schema coverage needs mainly a statement of what comes back, and the description supplies that by naming the template/schedule split and key sub-fields. Not quite complete because it says nothing about error or empty-result behavior, but nothing essential to invoking it is missing.

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 coverage is 100% and the single parameter already documents itself and points at crunch_list_recurring_expenses for discovery. The description adds no further interpretation of recurring_expense_id, so the baseline 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?

Names a specific verb and resource ('Get a recurring expense') and goes on to define what 'in full' means: the template expense (supplier, lines, payment) plus its schedule (recurringEvent). That content breakdown distinguishes it from the plain crunch_get_expense and from crunch_list_recurring_expenses without naming either.

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: 'in full' signals a detail fetch for a known ID, contrasting with recovery of a listing. There is no explicit when-to-use or when-not-to-use statement, and no mention of when crunch_get_expense should be chosen instead. The pointer to crunch_list_recurring_expenses lives in the schema, not the description.

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