Skip to main content
Glama

MaxRechnung

Rechnung aus Vorlage erstellen

create_invoice_from_template

Tarif: ab Business (darunter antwortet die API mit plan_required).

Rechnung aus Vorlage erstellen

Legt einen Entwurf an: nächste freie Nummer, Rechnungs- und Leistungsdatum heute (oder invoice_date), Absender aus dem Firmenprofil. Ist die Vorlage an einen Kunden gebunden, kommen die Empfängerdaten aktuell aus dem Kunden. Braucht invoices:draft und templates:read; zählt wie jede neue Rechnung ins Monatskontingent. Antwort ist die neue Rechnung.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "create_invoice_from_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesInterne `id` der Rechnungsvorlage (UUID), aus `GET /invoice-templates`.
bodyNoJSON-Request-Body.
_idempotency_keyNoOptional. Geht als Header `Idempotency-Key` an die API: derselbe Wert mit demselben Aufruf liefert 24 Stunden lang die erste Antwort zurück, statt den Vorgang zu wiederholen. Bei einem Wiederholversuch denselben Wert schicken.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses that only a draft is created, that the next free number is assigned automatically, that dates default to today, that the sender comes from the company profile, that recipient data is taken from the bound customer, that both 'invoices:draft' and 'templates:read' scopes are required, and that the call consumes the monthly invoice quota. This is exactly the kind of side-effect, permission, and billing context annotations cannot express.

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?

The body is dense and largely front-loaded, with the plan gate placed first and the creation semantics following. Minor waste: the heading 'Rechnung aus Vorlage erstellen' merely repeats the title, and the plan-tier sentence is separated from the rest by a blank line, slightly fragmenting the flow.

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 create/mutation tool with no output schema, the description covers defaults, permission requirements, quota impact, plan gating and states that the response is the new invoice — enough to call it correctly. What remains unaddressed is the lifecycle after creation (how the draft is finalized or sent) and how it relates to the near-identical draft-creation sibling.

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%, so the schema already documents id, invoice_date and _idempotency_key including their formats and defaults. The description restates the invoice_date default ('heute') but adds no new syntax or constraint information, 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?

The description names a specific verb and resource ('Rechnung aus Vorlage erstellen') and immediately clarifies the output is a draft, not a finalized invoice. It does not, however, differentiate itself from the sibling 'create_invoice_draft' or explain how the two differ, leaving an agent to infer the distinction.

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?

It states a hard prerequisite — the plan must be Business or higher, otherwise the API returns plan_required — which is genuinely useful gating information. But there is no explicit when-to-use versus alternatives guidance, e.g. when to create from a template rather than call create_invoice_draft or add_invoice_items_from_template afterwards.

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