Skip to main content
Glama

MaxRechnung

Kunde löschen

delete_customer
Destructive

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

Kunde löschen

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

Input Schema

NameRequiredDescriptionDefault
idYesPfad-Parameter id

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=true, so the agent knows this is a destructive write. The description adds real value with the plan gate: below Pro the API returns plan_required, a failure mode not visible in the schema or annotations. However, it says nothing about irreversibility, whether related records (invoices, drafts) are affected, or whether confirmation is required.

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?

The text is very short and the plan constraint is front-loaded, which is good. But one of its two lines merely echoes the title, so part of the description does not earn its place.

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 destructive, irreversible customer deletion with no output schema, the description should disclose consequences such as dependent records or restoration options. Only the plan gate is covered, leaving the agent under-informed about the impact of invoking it.

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?

Only one parameter (id, UUID) exists and schema description coverage is 100%, so the schema fully carries the parameter burden. The description adds nothing about identifier semantics, so the baseline 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?

The final line "Kunde löschen" simply restates the tool title and name in German, adding no verb-plus-resource detail beyond what the identifier already conveys. The only substantive content is the plan gate, not a description of what deletion entails.

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?

There is no guidance on when to use this versus siblings such as delete_sales_document or the customer lifecycle tools (create/update/get_customer). The plan prerequisite is stated, but that is an eligibility constraint rather than when-to-use guidance, and no alternatives or preconditions are named.

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