Skip to main content
Glama

MaxRechnung

USt-IdNr. des Kunden prüfen und festhalten

check_customer_vat_id

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

USt-IdNr. des Kunden prüfen und festhalten

Prüft vat_id serverseitig (qualifiziert per BZSt, wenn die eigene USt-IdNr. aus dem Firmenprofil deutsch ist, sonst VIES) und schreibt das verifizierte Ergebnis nach vat_id_check. Bodylos. Antwort ist der aktualisierte Kunde.

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

Input Schema

NameRequiredDescriptionDefault
idYesPfad-Parameter 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

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false / destructiveHint=false; the description goes well beyond that by disclosing the plan gate and error code, the dual verification path (BZSt when the company profile's own VAT ID is German, VIES otherwise), the write target field `vat_id_check`, and that the call is bodyless. What it omits is what values `vat_id_check` can take and whether a re-check overwrites prior results.

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?

Front-loaded with the plan restriction, then purpose, then mechanics, then return value — a logical order with no filler. The only redundancy is the heading line that repeats the tool title verbatim.

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?

With no output schema, the description correctly states the return value ('Antwort ist der aktualisierte Kunde') and covers the plan gate, verification provider choice, and write destination. It is nearly complete; the missing piece is the set of possible `vat_id_check` outcomes an agent would need to interpret the result.

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% and the `_idempotency_key` description is already detailed, so the schema carries the parameter burden. The description's only added parameter-level information is '**Bodylos.**', which usefully confirms there is no request body, but that is a thin increment over structured data.

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?

States a specific verb+resource ('USt-IdNr. des Kunden prüfen und festhalten') and adds the mechanism: server-side verification via BZSt or VIES, with the result persisted to `vat_id_check`. The customer scoping ('des Kunden', 'aktualisierte Kunde') distinguishes it from the standalone check_vat_id sibling, though no sibling is named explicitly.

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?

Gives a real precondition — the tool requires the Business plan and otherwise returns `plan_required` — which helps an agent decide feasibility. It implies the use case (persist a verified VAT ID on a customer) but never states when to prefer this over check_vat_id or check_invoice_recipient_vat_id, leaving the alternative selection to inference.

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