Skip to main content
Glama

MaxRechnung

Kunde anlegen

create_customer

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

Kunde anlegen

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

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

C2.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write/non-destructive profile is covered structurally. The description does add one genuine behavioral fact beyond that: the Pro plan requirement and the plan_required error response, which an agent cannot infer elsewhere. It says nothing about returned identifiers, side effects, or tier-gated fields failing with 403.

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?

It is short and the plan constraint is front-loaded, so there is little wasted text. But the second sentence is pure duplication of the title, and brevity here reflects under-specification rather than economy.

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

Completeness2/5

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

For a create tool with a large nested body (address, VAT scheme, e-invoice profiles, custom_fields merge semantics) and no output schema, the description omits what a caller most needs at the top level: that name is the sole required field, what a successful response returns, and which fields are Business-tier versus Pro-tier. The rich schema rescues some of this, but the description itself is far too thin.

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 schema already documents the body, idempotency key, and every nested field including tier gating. The description adds no parameter meaning at all, which is the baseline 3 when the schema carries the full burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description's only content about the action is "Kunde anlegen", which is a verbatim repeat of the title and a literal restatement of the tool name create_customer. It conveys no scope, no distinction from update_customer or create_sales_document, and no detail about what a created customer comprises.

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

Usage Guidelines2/5

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

The only guidance offered is a plan gate: "ab Pro (darunter antwortet die API mit plan_required)" — a prerequisite, not a when-to-use rule. Nothing says when to create a new customer versus updating an existing one, nor that check_customer_vat_id / check_iban might be worth calling first.

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