Skip to main content
Glama

MaxRechnung

Beleg anlegen

create_sales_document

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

Beleg anlegen

Legt ein Angebot (ab Pro), eine Auftragsbestätigung oder einen Lieferschein (beide ab Business) als Entwurf an. Felder wie bei der Rechnung; der Beleg kennt kein Zahlungsziel und keine E-Rechnung. Scope invoices:draft. Angebote sind ab Pro, Auftragsbestätigungen und Lieferscheine ab Business: unter Pro antwortet jeder /sales-documents-Endpunkt mit 403 plan_required; in Pro ebenso, wer eine Auftragsbestätigung oder einen Lieferschein anlegt, deren Status setzt oder dorthin weiterführt (details nennt type bzw. target).

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

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/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description goes well beyond them by disclosing the required scope, the plan gating and exact failure mode (403 plan_required with `details` naming `type`/`target`), and that the result is a draft. It does not say what the draft's initial status is or what the call returns, so it stops short of full behavioral disclosure.

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?

The plan gating is stated twice: once up front ("ab Pro … darunter antwortet die API mit plan_required") and again in the closing sentence ("Angebote sind ab Pro … 403 plan_required"), so one sentence does not earn its place. The rest is compact and the key constraint is front-loaded, but the duplication costs it.

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 tool with no output schema and a deeply nested body whose schema already carries 100% coverage, the description covers the essential external concerns: permissions, plan limits, and what this document type does not support. It omits what is returned (draft identifier) and how the draft is later finalized, which the agent must discover elsewhere.

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 per-field semantics (skonto, vat_scheme, custom_fields, idempotency key) are already documented in the structured data. The description adds only framing — that the field set mirrors an invoice but without payment terms or e-invoice fields — which is useful but marginal. Baseline 3 applies.

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 names a specific verb+resource ("Legt ein Angebot … eine Auftragsbestätigung oder einen Lieferschein … als Entwurf an") and immediately scopes it by plan tier. It explicitly separates this tool from the invoice family by noting "Felder wie bei der Rechnung; der Beleg kennt kein Zahlungsziel und keine E-Rechnung." An agent can distinguish it from create_invoice_draft and update_sales_document without opening the schema.

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 usage conditions: quote requires Pro, order confirmation and delivery note require Business, and every /sales-documents endpoint returns 403 plan_required below that. It also states the required scope `invoices:draft`. What is missing is routing guidance toward siblings (e.g. update_sales_document for later edits, update_sales_document_status to set status), which is only implied by the plan-tier warning.

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