Skip to main content
Glama

Read one fixed cost

recurring_get
Read-onlyIdempotent

Read a single fixed-cost template with its splits by id to retrieve the current nextDueAt before updating or advancing it. Use when the template id is already known; read-only.

Instructions

Read one fixed-cost template with its splits, by id. Use it to get the current nextDueAt before recurring_update or recurring_advance; use recurring_list when you do not know the id yet. Read-only. Answers 404 recurring_expense_not_found for an unknown id or an id of another flat.

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": {
      "id": "<id>"
    },
    "name": "recurring_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId of the fixed-cost template, as returned in recurringExpenses[].id by recurring_list or in recurringExpense.id by recurring_create.
wgCodeNoShare code of the flat (code from wg_list). Leave it out when the account belongs to one flat.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / id / description
      Added value: +"Id of the fixed-cost template, as returned in recurringExpenses[].id by recurring_list or in recurringExpense.id by recurring_create."
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so 'Read-only' is largely redundant. What the description adds beyond them is real operational context: the returned payload includes splits and nextDueAt, and an unknown id or an id belonging to another flat yields a 404 recurring_expense_not_found — useful for scoping and error handling.

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?

Front-loaded with purpose, then usage, then error behavior — good ordering in a short span. The 'Read-only' sentence duplicates the annotations and is the only non-earning line.

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 two-parameter read tool with no output schema, it covers what's returned (template with splits, nextDueAt), the sequencing use case, and the failure mode. It stops short of describing the full response shape or whether splits are scoped, but the essentials for correct invocation are present.

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 id and wgCode are already fully documented. The description adds only 'by id' and an implicit hint about flat scoping via the 404 behavior; nothing about wgCode or its optionality beyond what the schema states.

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

Purpose5/5

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

States a specific verb and resource — 'Read one fixed-cost template with its splits, by id' — and immediately contrasts with recurring_list. An agent can distinguish this single-resource getter from sibling readers without inspecting any schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use routing: fetch it to obtain the current nextDueAt before recurring_update or recurring_advance, and use recurring_list when the id is unknown. Both the trigger and the alternative are named.

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