Skip to main content
Glama
office-books-mcp

office-books-mcp

by mjmirza

List recurring invoice templates

list_recurring_templates
Read-only

Retrieve paginated templates for recurring invoices to review scheduled billing setups in a connected Lexware Office account.

Instructions

List templates for recurring invoices.

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_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo0-based page index
sizeNoPage size, 1 to 250, Lexware default 25

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

C2.4/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: it does not mention pagination defaults, ordering, or what a returned template record carries, which is the kind of context that would justify its existence here.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short, front-loaded sentence with no wasted words, but the brevity comes from under-specification rather than from efficient communication. There is no structure beyond the bare statement of purpose.

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?

This is a simple read-only, zero-required-parameter list tool whose parameters are fully documented by the schema and whose safety profile is covered by annotations, so the minimum is met. However, with no output schema, the description should say something about what a template record looks like or how results are paged, and it does not.

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%: page is documented as a 0-based index and size as 1 to 250 with a Lexware default of 25. The description adds no further parameter meaning, so the baseline of 3 applies since the schema does the work.

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

Purpose2/5

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

The sentence 'List templates for recurring invoices' only expands the name list_recurring_templates and the title 'List recurring invoice templates' into slightly different words. It gives no scope, no indication of what a template contains, and nothing that distinguishes this from the sibling list_* tools.

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, no mention of alternatives (e.g. listing vouchers or sales documents to see actual recurring invoices), and no prerequisites. The agent must infer the tool's role from the name alone.

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