Skip to main content
Glama

MaxRechnung

Rechnungsvorlagen auflisten

list_invoice_templates
Read-only

Tarif: in jedem Tarif (Free, Pro, Business).

Rechnungsvorlagen auflisten

Gespeicherte Rechnungen ohne Nummer und Daten: Empfänger, Positionen, Steuerregelung, Zahlungsziel, Hinweis. Neue Rechnung daraus: POST /invoice-templates/{id}/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_invoice_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoQuery-Parameter limit
offsetNoQuery-Parameter offset

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: no plan gating, and the fact that templates carry no invoice number or dates. It says nothing about ordering, pagination metadata or the shape of returned entries, so it is useful but incomplete.

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?

Very short, but poorly structured: the title is repeated verbatim as a standalone line, and the remaining content is a chain of noun fragments without verbs. Nothing is wasted in length, yet the fragments cost readability and push the most useful fact (the follow-up endpoint) to the very end.

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 read-only, two-parameter list tool with full schema coverage and no output schema, the description covers purpose, plan availability, the nature of the returned entities, and the next workflow step. Only paging/return-format detail is missing, which the schema largely absorbs.

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% and both parameters (limit, offset) are already documented with defaults and bounds in the schema. The description adds nothing about paging semantics or maximum page size, so the baseline of 3 applies.

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?

Names a specific verb+resource ('Rechnungsvorlagen auflisten') and clarifies what a template actually is: a stored invoice without number and dates, containing recipient, line items, tax scheme, payment terms and note. That is genuine resource disambiguation. It does not, however, distinguish itself from siblings such as list_item_templates or list_sales_documents, so 4 rather than 5.

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

Usage Guidelines3/5

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

Gives plan availability ('in jedem Tarif') and points to the concrete follow-up path `POST /invoice-templates/{id}/invoices`, which implies the main reason to list templates. It never states when to prefer this over another list endpoint or what the templates cannot be used for, so usage is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources