Skip to main content
Glama

Periodieke facturen

list_recurring_invoices
Read-only

Retrieve recurring invoices with their billing interval and next issue date to plan cash flow and confirm which invoices repeat automatically.

Instructions

The invoices that repeat, with their interval 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": "list_recurring_invoices"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered without help from the description. The description adds useful context about what the response contains (interval and next date), but says nothing about ordering, whether paused/inactive schedules are included, or whether these are templates versus generated invoices.

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?

A single short sentence with no filler, and the identifying information ('invoices that repeat') is front-loaded. It may be slightly too terse given the open questions about scope, but no sentence is wasted.

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

Completeness3/5

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

For a zero-parameter read-only list tool with no output schema, the description covers the essentials by naming the returned fields. It still leaves open whether paused schedules or historical instances are included and what order results arrive in, which matters for an agent deciding whether to rely on it.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The empty schema is consistent with the description's implication of a simple unfiltered listing.

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?

The description names the specific resource ('the invoices that repeat') and distinguishes it from the sibling list_invoices by the recurring qualifier, and it states what data comes back (interval, next date). It lacks an explicit verb such as 'list', but the noun phrase plus the returned fields make the purpose unambiguous.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no mention of alternatives such as list_invoices for one-off invoices or save_recurring_invoice for creating them. The agent must infer the selection criteria entirely from the tool name and the word 'repeat'.

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