Skip to main content
Glama

MaxRechnung

Empfänger-USt-IdNr. prüfen und festhalten

check_invoice_recipient_vat_id

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

Empfänger-USt-IdNr. prüfen und festhalten

Prüft recipient.vat_id serverseitig (qualifiziert per BZSt, wenn sender.tax_id eine deutsche USt-IdNr. ist, sonst VIES) und schreibt das Ergebnis inkl. Prüf-Schnappschuss nach recipient.vat_id_check. Bodylos. Nur am Entwurf — festgeschriebene Belege frieren die Empfängerangaben ein (dafür GET /check/vat). Antwort ist die aktualisierte 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": "check_invoice_recipient_vat_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesInterne `id` der Rechnung (UUID), nicht die Belegnummer. Zu einer Nummer (z. B. `RE-2026-0004`) liefert `GET /invoices?number=…` (MCP: `list_invoices` mit `number`) die `id`.
_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.4/5.0
Behavior4/5

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

Adds substantial behavior beyond the annotations: the call is bodyless, it mutates the draft by writing a check snapshot into `recipient.vat_id_check`, and the response is the updated invoice. The plan gate and draft-only restriction are also behavior an annotation could not convey. Minor gap: it does not say what happens if the VAT ID is invalid (does the write still occur?), which matters for a state-changing call flagged 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.

Conciseness4/5

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

The operative sentence is dense and informative, and the constraints are front-loaded. However, the title 'Empfänger-USt-IdNr. prüfen und festhalten' is repeated verbatim as a heading line inside the description, which is pure duplication of structured data and costs a line.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation with no output schema, the description covers the prerequisite (Business plan), the precondition (draft only), the side effect (write to `recipient.vat_id_check`), and the return value (updated invoice). Nothing an agent needs to invoke it correctly is missing.

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 both `id` and `_idempotency_key` are fully documented in the schema, including how to resolve a document number to an id via `list_invoices`. The description adds nothing further about parameters, so the baseline of 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?

Names a specific verb and object ('Prüft `recipient.vat_id` serverseitig ... und schreibt das Ergebnis ... nach `recipient.vat_id_check`') and states the mechanism (BZSt qualified vs. VIES depending on `sender.tax_id`). It also scopes the tool to drafts only, which separates it from sibling checks like check_customer_vat_id or check_vat_id without needing to open a schema.

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

Usage Guidelines5/5

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

Explicitly says when it may be used ('Nur am Entwurf') and when not (finalized invoices freeze recipient data), naming the alternative route `GET /check/vat` for that case. It also states the plan prerequisite up front, including the exact failure code `plan_required`, so an agent knows when the call will be rejected.

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