Skip to main content
Glama

Read fixed costs

recurring_list
Read-onlyIdempotent

Lists fixed-cost recurring expense templates ordered by next due date, so you can find a template ID or see which flat costs are due next. Read-only.

Instructions

List all fixed-cost templates (recurring expenses such as rent or internet) of the flat, ordered by nextDueAt, at most 500. Use it to find a template id or to see what is due next; use recurring_get for a single template and expenses_list for charges that were already booked. Read-only. Each entry has description, category, amountCents, paidByMemberId, intervalMonths, nextDueAt, pausedAt (null when active) and splits; currency is always EUR.

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
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. First observedv0.1.0

TDQS

A4.5/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 partly redundant, but the description adds real context the annotations lack: the ordering, the 500-entry ceiling, the exact returned fields, and the fact that currency is always EUR. It does not explain what happens past 500 entries (truncation vs. error), which is the one behavioral gap left.

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 tight sentences: scope first, routing second, return shape third. No filler, and the most decision-relevant facts (what it lists, when to prefer a sibling) are front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by enumerating every returned field including the pausedAt-null semantics and the fixed EUR currency. For a single-optional-parameter read tool, nothing an agent needs in order to call or interpret 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 wgCode parameter is fully documented in the schema, including its pattern and the rule about omitting it for single-flat accounts. The description adds nothing about the parameter, so the baseline 3 applies.

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 ("List all fixed-cost templates") with a parenthetical definition of what a fixed-cost template is, plus ordering (nextDueAt) and a hard cap (500). It also names the siblings it is not — recurring_get and expenses_list — so an agent can separate it from lookalikes without opening a 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 two concrete use cases (finding a template id, seeing what is due next) and explicitly routes to recurring_get for a single template and expenses_list for already-booked charges. The when-not conditions are stated, not inferred.

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