Skip to main content
Glama

Meistron

by app.meistron

Rechnung anlegen

rechnung_anlegen

Legt einen Rechnungs-ENTWURF an. Ein Entwurf hat noch KEINE Rechnungsnummer und ist frei änderbar — die Nummer wird erst beim Versenden vergeben, damit der Nummernkreis lückenlos bleibt. Verschickt NICHTS an den Kunden.

Wird ein Auftrag angegeben, übernimmt der Entwurf dessen Material und erfasste Arbeitszeit als Positionen — das ist der übliche Weg. Zusätzlich oder stattdessen können eigene Positionen angegeben werden.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hinweisNoText für den Kunden auf der Rechnung.
kunde_idNoDie Kennung des Kunden. Ohne Angabe wird der Kunde des Auftrags übernommen.
auftrag_idNoAuftrag, dessen Material und Arbeitszeit übernommen werden sollen.
positionenNoEigene Positionen. Höchstens 50.
steuersatzNoSteuersatz für den GESAMTEN Beleg in Prozent — 19, 7 oder 0. Ohne Angabe der im Betrieb hinterlegte Satz. Ein Beleg trägt genau EINEN Satz, im Kopf wie in jeder Position; gemischte Sätze lehnt Meistron beim Finalisieren ab. Wer beides braucht, legt zwei Belege an.
ohne_zeitenNoAuf true setzen, wenn NUR das Material übernommen werden soll, keine Stunden.
ohne_materialNoAuf true setzen, wenn NUR die Stunden übernommen werden sollen.
idempotency_keyNoIm vollautonomen Betrieb erforderlich. Beim ersten Aufruf weglassen: Der Server liefert dann einen UUID-Key, ohne die Aktion auszuführen. Den Aufruf mit diesem Key wiederholen und bei Retry/Reconnect denselben Key verwenden. Eine neue beabsichtigte Aktion braucht einen neuen Key.

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description reveals key behavior: a draft has no invoice number until sending, is freely editable, nothing is sent to the customer, and order-linked material/time are converted into line items. This gives an agent the needed mental model for draft creation. It is consistent with readOnlyHint=false.

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

Conciseness5/5

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

Two short, dense paragraphs: the first states the core draft behavior and non-sending guarantee, the second explains the creation paths. Every sentence adds information and the most important fact (draft creation) is front-loaded.

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?

The description covers the essential behavioral and selection context for a complex optional-parameter tool, and the input schema fills in all parameter details. It does not mention the return value or the idempotency-key handshake in the description itself, but those are not needed for tool selection and the schema covers the handshake.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all eight parameters. The description adds useful semantic context by explaining how auftrag_id relates to positionen (order material and recorded hours are adopted as line items), and that custom positions can supplement or replace them.

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 starts with a concrete verb and resource: 'Legt einen Rechnungs-ENTWURF an.' It then clarifies the draft's defining properties (no invoice number yet, freely editable) and explicitly states 'Verschickt NICHTS an den Kunden,' distinguishing it from sending tools like rechnung_versenden.

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 selection context: an order can supply material and time entries, 'das ist der übliche Weg,' and custom positions can be added instead or as well. It does not explicitly name sibling tools such as rechnung_versenden as the follow-up action, though 'Verschickt NICHTS' strongly implies sending is done separately.

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

All Meistron toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool name clearly identifies a distinct resource (Angebot, Auftrag, Rechnung, Material, etc.) and action. Even potentially similar pairs like material_buchen and material_zuweisen are explicitly differentiated in their descriptions, so an agent can reliably select the correct tool.

Naming Consistency5/5

All tool names follow a consistent resource_action pattern in lowercase with underscores (e.g., kunde_anlegen, material_suchen). A few status/query tools like betrieb_ueberblick and datei_stand use noun compounds, but these are consistently used for state queries and do not break the overall convention.

Tool Count3/5

With 23 tools, the server falls into the 'heavy' range of 16-25. While the breadth of a handwerker management system justifies many operations, the count is high and some areas (like customer management) are underrepresented, making the set feel larger than necessary.

Completeness3/5

The core order-to-invoice workflow is well covered, but there are notable gaps: no customer search or update, no conversion from Angebot to Rechnung, and no ability to change order status. These are significant omissions that agents must work around, even though the descriptions clearly state these limitations.

Resources