Skip to main content
Glama

getecoback-raumklima

kontaktgrill_platten_spuelmaschine_beleg

Read-only

Spülmaschinenfreigabe abnehmbarer Kontaktgrillplatten für dokumentierte Modellvarianten nachschlagen — Look up the exact documented contact-grill plate cleaning claim.

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

Input Schema

NameRequiredDescriptionDefault
modellYesExakte Produktvariante aus dem redaktionellen Katalog.

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 and closed-corpus behavior are covered structurally. The description reinforces this with 'dokumentierte' and 'exact documented ... claim', signalling an authoritative catalog lookup rather than a computed answer, but says nothing about what the returned claim looks like or what happens for 'unbekannt'.

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 compact line with the resource front-loaded and the verb at the end, plus a bilingual restatement that adds little but costs few tokens. No filler beyond the duplicated German/English phrasing.

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?

For a one-parameter, closed-enum read tool this is close to sufficient, but with no output schema the description should at minimum hint at what a 'claim' returns (a yes/no approval, a text passage, an absence marker). The meaning of the 'unbekannt' enum value is also left for the agent to guess.

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% with a fully enumerated 'modell' parameter, so the baseline is 3. The description adds only the framing that the variants are the documented editorial catalog, which is mild reinforcement of the enum rather than new meaning about format or matching behavior.

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?

States a specific verb ('nachschlagen' / 'look up') and a narrowly scoped resource: the dishwasher-suitability claim for removable contact-grill plates, restricted to documented model variants. That is clearly distinct from the appliance-adjacent siblings (loading comparison, hand-wash costs, drain path). It stops short of naming a sibling it is not, so 4 rather than 5.

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 phrase 'für dokumentierte Modellvarianten' implies the tool only applies when the model is in the editorial catalog, which is a useful implicit boundary. However, there is no explicit when-to-use / when-not-to-use instruction and no pointer to an alternative for undocumented models, even though the enum contains an 'unbekannt' fallback whose role is left unexplained.

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