Skip to main content
Glama

getecoback-raumklima

spuelerkorb_auszug_notierter_tuer_und_arbeitsweg

Read-only

Bei dokumentiert vollständig geöffneter Tür den Korbauszug getrennt vom benötigten Standplatz prüfen — Keep the user’s working space separate from physical basket travel.

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": {
      "lichte_tiefe_mm": "<lichte_tiefe_mm>",
      "tuer_belegt_mm": "<tuer_belegt_mm>",
      "korb_belegt_mm": "<korb_belegt_mm>",
      "greifraum_mm": "<greifraum_mm>",
      "gleiche_front_und_stellung": "<gleiche_front_und_stellung>"
    },
    "name": "spuelerkorb_auszug_notierter_tuer_und_arbeitsweg"
  }
}

Input Schema

NameRequiredDescriptionDefault
greifraum_mmYesEigener vor Ort bemessener zusätzlicher Arbeitsraum vor dem Auszug.
korb_belegt_mmYesGemessener Raumanspruch des vollständig ausgezogenen Korbs ab Front.
tuer_belegt_mmYesGemessener Raumanspruch der geöffneten Tür ab Front.
lichte_tiefe_mmYesFreie Tiefe ab geprüfter Gerätefront bis zum Hindernis.
gleiche_front_und_stellungYesGleicher Nullpunkt und tatsächlich belegte Tür- und Korbstellungen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

The readOnlyHint=true and openWorldHint=false annotations already establish that this is a safe, non-open-world read/check operation. The description adds that the check requires a documented fully open door and separates basket travel from the user's working space, but it does not explain the result, assumptions, or failure conditions, so it adds only moderate behavioral context beyond the annotations.

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?

The description is short, front-loads the condition ('Bei dokumentiert vollständig geöffneter Tür'), and contains no padding. Its structure is slightly weakened by the German/English mix and the abstract second clause, but it remains efficient.

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 five-parameter measurement/check tool with no output schema, the description should explain what 'prüfen' produces, such as a pass/fail result or clearance assessment. Instead it only states the scenario and a high-level principle, leaving the return behavior and decision logic 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?

Schema description coverage is 100%, and all five parameters are individually documented in the schema. The description mentions door and basket dimensions only in general terms and adds no syntax, units, or interpretation beyond what the schema already provides, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies a specific check involving the basket pull-out, the fully opened door, and the required standing space, so it is more than a tautology. However, it never states what the tool actually returns or how the check is evaluated, and the mixed German/English wording makes the intended operation less crisp than it could be.

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 'Bei dokumentiert vollständig geöffneter Tür' gives an implied usage condition: use this when the door is documented as fully open. But there is no explicit when-not guidance, no prerequisites, and no comparison to the similar sibling tool dealing with shared operating space, so the agent must infer the routing.

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