Skip to main content
Glama

Read the reminder history

reminders_list
Read-onlyIdempotent

Lists a flat's payment reminders from the last 30 days, newest first, showing channel, message, amount, debt age and sent time. Check recent reminder activity before sending a new one.

Instructions

Lists the payment reminders sent in the flat in the last 30 days, newest first, at most 50, each with channel, message, amountCents, currency, oldestDebtAgeDays and sentAt. Read only. Use it to check whether a reminder went out recently before calling reminder_send (which has a 48 h cooldown per debtor); for who owes the caller money use balances_get.

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": "reminders_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 establish readOnly, idempotent, non-destructive; the description reinforces 'Read only' and adds real behavior beyond annotations: 30-day window, newest-first ordering, max 50 results, and listed response fields. It does not explain pagination when more than 50 exist, so it stops short of a full 5.

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?

The description is front-loaded with scope and output shape, then the usage routing. Sentences are dense but each adds actionable information; 'Read only' is slightly redundant with annotations but negligible.

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?

For a one-optional-parameter read tool with no output schema, the definition supplies the missing return context (fields, ordering, cap, time window), usage guidance, and alternatives. Nothing material to correct invocation 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?

The only parameter, wgCode, has full schema coverage with a clear description and fallback when the account belongs to one flat. The tool description does not mention wgCode or add semantics beyond 'in the flat', so the schema does the work and baseline 3 is appropriate.

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?

The description opens with a specific verb and resource ('Lists the payment reminders sent in the flat'), then pins down the time window, ordering, cap, and returned fields. It distinguishes the tool from reminder_send and balances_get so an agent can select it without opening the 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?

It gives an explicit use case: check whether a reminder went out recently before calling reminder_send, and names the 48 h per-debtor cooldown as the reason. It also routes the agent to balances_get for who owes money, providing a clear alternative.

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