Skip to main content
Glama

getecoback-climate-weather

spuelmaschine_ablaufweg_anleitung

Read-only

Geplanten Spülmaschinen-Ablaufweg mit den dokumentierten Höhen- und Längengrenzen abgleichen — Check dishwasher drain route measurements against the exact provided manual limits.

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": {
      "hoehe_cm": "<hoehe_cm>",
      "schlauch_cm": "<schlauch_cm>",
      "min_hoehe_cm": "<min_hoehe_cm>",
      "max_hoehe_cm": "<max_hoehe_cm>",
      "max_schlauch_cm": "<max_schlauch_cm>"
    },
    "name": "spuelmaschine_ablaufweg_anleitung"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoehe_cmYesGemessene Bezugshöhe am Ablauf nach Definition der Geräteanleitung in cm.
schlauch_cmYesVorgesehene gesamte Schlauchlänge in cm.
max_hoehe_cmYesLaut Anleitung größtzulässige Ablaufhöhe in cm.
min_hoehe_cmYesLaut Anleitung kleinstzulässige Ablaufhöhe in cm.
max_schlauch_cmYesLaut Anleitung größtzulässige Schlauchlänge in cm.

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 locality are covered. The description adds only that the limits are the 'exact provided manual limits' — i.e. they are inputs, not looked up internally — but says nothing about what a violation result looks like or how boundary equality is treated.

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 description is short, but the German sentence and its English rendering say essentially the same thing, so roughly half the text is redundant. The core action is front-loaded, which keeps it usable.

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

Completeness4/5

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

For a read-only five-number validation tool with full schema coverage and no output schema, the definition gives enough to invoke it correctly: what to pass in and that the limits come from the manual. The only gap is the outcome semantics, which a caller might reasonably want to know.

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 every parameter is already documented with units and ranges. The description reinforces that the min/max values must come from the device manual rather than being chosen by the agent, which is a small but real addition beyond the schema; baseline 3 applies.

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?

Names a specific verb (abgleichen/check) and a specific resource (the planned dishwasher drain route versus documented height/length limits). An agent can tell this is a constraint-validation tool rather than a lookup or a calculation, though the description does not name any sibling it differs from.

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?

'Geplanten ... Ablaufweg ... abgleichen' implies the use case: a planned/measured route is validated. It does not state when not to use it, what to do if limits are missing, or which sibling handles related dishwasher questions, so usage is only implied rather than directed.

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