Skip to main content
Glama

getecoback-raumklima

gebrauchtgeraet_wartungsbeleg_zielbauteil_gegen_kit

Read-only

Einen Servicebeleg auf den darin ausdrücklich genannten Teil eines mehrteiligen gebrauchten Sets begrenzen — Check which sold assemblies are actually covered by a maintenance receipt.

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": {
      "beleg_diesem_set_zugeordnet": "<beleg_diesem_set_zugeordnet>",
      "geraet": "<geraet>",
      "station": "<station>",
      "einsatzteil": "<einsatzteil>"
    },
    "name": "gebrauchtgeraet_wartungsbeleg_zielbauteil_gegen_kit"
  }
}

Input Schema

NameRequiredDescriptionDefault
geraetYesErwähnung des Grundgeräts.
stationYesErwähnung der für den Kauf entscheidenden Station.
einsatzteilYesErwähnung des entscheidenden lose mitgegebenen Einsatzteils.
beleg_diesem_set_zugeordnetYesKann der Beleg nachweislich diesem verkauften Satz zugeordnet werden?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered by structured data. The description adds that the operation is a scoping/coverage determination rather than a fetch, but 'begrenzen' (limit) is ambiguous enough that an agent could misread it as a mutation without the read-only annotation. It says nothing about what the tool returns, despite there being no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence states the scoping rule, with an English restatement after an em dash for orientation. It is compact and free of filler, though the dual-language phrasing reads as two framings rather than one crisp definition.

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

Completeness3/5

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

With four required classification parameters and no output schema, the description should convey what judgment the inputs produce — e.g., how an enum value of 'nicht_teil_des_angebots' affects the outcome. The safety profile is covered by annotations and the parameters by the schema, but the resulting verdict and its interpretation are left unstated.

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 all four parameters (three enums plus the boolean assignment check) are already documented. The description's phrase 'ausdrücklich genannten Teil' loosely gestures at the pflege_explizit / nur_erwaehnt / offen enum semantics, but adds no explanation of how those values combine into a conclusion. Baseline 3 is correct.

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 names a specific operation (restricting a service/maintenance receipt to the explicitly named component of a multi-part used set) rather than a tautology. The English gloss ('Check which sold assemblies are actually covered by a maintenance receipt') adds a second, slightly different framing, but both converge on determining coverage scope, which an agent can act on. Sibling differentiation comes only from the dense name suffix 'gegen_kit', not from the prose.

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

Usage Guidelines3/5

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

The description implies a scenario — a receipt for a multi-part set where only one part is explicitly named — which is a usable trigger. It does not state when NOT to use it or point to any alternative for the related used-device evidence checks that the sibling list suggests exist. Guidance is inferable but not explicit.

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