Skip to main content
Glama

Kunde anlegen

create_customer

Neuen Kunden in der Kartei anlegen. Vorher mit list_customers prüfen, ob es ihn schon gibt.

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": {
      "name": "<name>"
    },
    "name": "create_customer"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
nameYesFirma oder Name
emailNo
phoneNo
streetNo
vat_idNo
countryNoISO-3166 Alpha-2, z. B. DE
is_businessNo
postal_codeNo
address_formNo
contact_titleNoTitel, steht vor dem Vornamen (Dr., Prof.)
buyer_referenceNoLeitweg-ID / Käuferreferenz (XRechnung)
contact_last_nameNo
contact_first_nameNo
contact_salutationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / contact_title
      Added value: +{
      +  "description": "Titel, steht vor dem Vornamen (Dr., Prof.)",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the mutation and safety profile is covered structurally. The description's only added behavior is the duplicate-check step; it says nothing about what happens on duplicate name collisions, whether partial records are accepted, or validation failures — modest added value beyond the annotations.

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 sentences with zero filler; the creation intent is front-loaded and the prerequisite follows immediately. Nothing is repeated from the title or annotations.

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 15 low-coverage parameters and no output schema, this is thinner than ideal — it doesn't explain the business-vs-private field split or the required minimum. Given that annotations carry the safety profile and the schema carries the fields, the description covers the essential intent and the one workflow rule that structured data cannot express.

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

Parameters2/5

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

Schema description coverage is only 27% across 15 parameters, so the schema leaves most fields undocumented, and the description compensates for none of them. It never mentions the required 'name', the 'is_business'/'vat_id' relationship, or the address_form and contact_salutation enums, leaving the agent to infer field semantics entirely.

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?

The description pairs a specific verb with a specific resource ('Neuen Kunden in der Kartei anlegen'), so an agent knows it creates a new customer record rather than updating or reading one. It does not explicitly contrast itself with update_customer or get_customer, but the word 'Neuen' plus the named prerequisite tool makes the intent unambiguous.

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 a concrete precondition ('Vorher mit list_customers prüfen, ob es ihn schon gibt'), which is a real when-to-use workflow and routes the agent to a sibling for the duplicate check. It stops short of saying what to do if a match is found (abort vs. update_customer), so it is not fully closed-loop guidance.

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