Skip to main content
Glama

MaxRechnung

Kunde abrufen

get_customer
Read-only

Tarif: in jedem Tarif (Free, Pro, Business).

Kunde abrufen

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": "get_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=true and destructiveHint=false, so the safe-read profile is covered structurally. The description's one addition is that the tool is available in every plan (Free, Pro, Business), which is genuine availability context but nothing about errors or lookup semantics for a missing customer.

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 front-loads the plan constraint, but one of the two sentences is a pure copy of the title and therefore does not earn its place. It is brief through under-specification rather than through disciplined editing.

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 read tool with no output schema, the description never indicates what is returned (which customer fields) or what happens on an unknown id, and it provides no clue about its relationship to the other customer tools. Annotations cover safety, but the retrieval contract remains undocumented.

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?

There is a single uuid parameter and schema description coverage is 100%, so the schema already carries the meaning. The description adds nothing about what the id identifies or how an unknown id behaves; baseline 3 applies when the schema does the work.

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 abrufen" is a verbatim restatement of the tool title and name, so it adds no descriptive content beyond the identifier. It does not distinguish this tool from siblings such as check_customer_vat_id or the create/update/delete_customer variants, nor does it say what a retrieved customer contains.

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 when-to-use guidance, no prerequisites and no routing to alternatives. The only contextual line concerns plan availability, which tells the agent who may call it but not when it is the right tool.

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