Skip to main content
Glama

MaxRechnung

Rechnung anlegen (Entwurf)

create_invoice_draft

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

Rechnung anlegen (Entwurf)

Legt immer einen Entwurf an. Zum Festschreiben anschließend PATCH /invoices/{id}/status. Scope invoices:draft (oder invoices:write).

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": "create_invoice_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A4.1/5.0
Behavior4/5

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

Beyond the annotations, the description discloses plan availability (Free, Pro, Business), required scope (`invoices:draft` or `invoices:write`), and the draft-only behavior with finalization as a separate step. It does not cover error cases or response details, but the annotations already establish that this is a non-read-only, non-destructive operation.

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 description is short and front-loads the plan availability and draft behavior. The repeated title line 'Rechnung anlegen (Entwurf)' is somewhat redundant with the tool title, but the overall structure is efficient.

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?

Given the very rich input schema, the description need not explain individual parameters. It adequately covers plan availability, permission scope, draft-only creation, and the finalization path, though it could mention what the creation returns or any notable failure modes.

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 input schema already carries the parameter semantics. The description itself adds no additional meaning about the `body` or `_idempotency_key` parameters, so the baseline score of 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 states a specific verb and resource: 'Rechnung anlegen (Entwurf)' and 'Legt immer einen Entwurf an.' It makes clear that the tool creates a draft invoice rather than finalizing or modifying one, which distinguishes it from the status-update and draft-update siblings.

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

Usage Guidelines4/5

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

It gives clear workflow guidance: always creates a draft, and finalization happens separately via `PATCH /invoices/{id}/status`. It does not explicitly name alternatives such as updating an existing draft, so it falls short of full when-to-use/when-not-to-use guidance.

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