Skip to main content
Glama

MaxRechnung

Kunde ändern

update_customer

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

Kunde ändern

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": "update_customer"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPfad-Parameter id
bodyNoJSON-Request-Body.

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/safety profile is known. The description adds genuinely useful information beyond that: the plan gate and the plan_required error response. It does not, however, disclose whether the update is partial or replacing, whether omitted fields are preserved, or whether changes are reversible.

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?

Two short fragments with no wasted prose, and the plan constraint is front-loaded. However, the brevity here reflects under-specification rather than efficient editing – the second line carries almost no information an agent doesn't already have from the name and title.

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 mutation tool with a large nested body object and no output schema, the description leaves the most consequential behavioral question unanswered: whether the body is a full replacement or a partial update. The plan gate is covered and the schema covers fields, but the update semantics an agent needs before calling it are 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% and the nested body properties are documented in detail in the schema itself, including plan tiers and merge/delete semantics for custom_fields. The description adds nothing beyond that, so the baseline of 3 applies.

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?

"Kunde ändern" is essentially a restatement of the tool name/title (update_customer / Kunde ändern) and gives no additional scope such as which attributes can be changed or what it does not cover. With siblings like create_customer, get_customer and delete_customer present, it does not distinguish itself from them at all.

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 is an eligibility note ("ab Pro", otherwise plan_required), which is a prerequisite rather than a when-to-use rule. Nothing tells the agent when to pick update_customer instead of create_customer or update_sales_document, or what to do if the plan is insufficient beyond the error code.

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