Skip to main content
Glama

getecoback-climate-weather

backofenauszug_obere_untere_kalte_greifspur

Read-only

Niedrigeren Abstand über einem kalten Blech vom tatsächlichen Greifraum davor unterscheiden — Compare the measured vertical access gap against a personal handling envelope.

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": {
      "kalte_anordnung_geprueft": "<kalte_anordnung_geprueft>",
      "unterkante_oben_mm": "<unterkante_oben_mm>",
      "oberkante_unten_mm": "<oberkante_unten_mm>",
      "greifraum_bedarf_mm": "<greifraum_bedarf_mm>"
    },
    "name": "backofenauszug_obere_untere_kalte_greifspur"
  }
}

Input Schema

NameRequiredDescriptionDefault
oberkante_unten_mmYesHöchster Punkt des unteren geplanten Blechaufbaus in derselben Stellung.
unterkante_oben_mmYesNiedrigster Punkt des oberen Elements in der beobachteten Stellung.
greifraum_bedarf_mmYesSelbst gemessener zusätzlicher vertikaler Raum für den vorgesehenen Kontrollgriff.
kalte_anordnung_geprueftYesSind beide belegten Ebenen und die Bewegungsstellung am kalten Aufbau eindeutig beobachtet?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 and the bar is lower. The description adds that a measured gap is checked against a personal envelope, but it never states how the gap is derived from the two edge measurements or what the verdict looks like.

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 sentence with no padding, front-loading the compared quantities. The German half is dense and grammatically tangled, which slightly blunts readability, but nothing is wasted.

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 no output schema, the description should say what the comparison yields (a verdict, a margin in mm, a pass/fail). It states the inputs being compared but leaves the return semantics entirely unspecified for a pure-computation tool.

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 are already documented in the schema; baseline 3 applies. The description's 'personal handling envelope' loosely maps to greifraum_bedarf_mm but adds no units, tolerances, or interpretation beyond what the schema says.

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 concrete operation: comparing a measured vertical access gap ('Abstand über einem kalten Blech') against a required handling envelope ('Greifraum'). The verb pair 'unterscheiden'/'compare' plus the two compared quantities makes the purpose inferable, though the German clause is convoluted and gives no cue to distinguish this from the many sibling backofenauszug_* tools.

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 statement of when to use this versus the closely named siblings (e.g. backofenauszug_kalte_paarstellung_bis_zum_anschlag). The 'unterscheiden ... vom tatsächlichen Greifraum' phrasing describes a conceptual distinction the tool performs, not guidance for the agent about when to select it.

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