Skip to main content
Glama

getecoback-climate-weather

dachfenster_oeffnung_spaltprofil_kitbereich

Read-only

Vergleicht drei statische Spaltmaße mit dem deklarierten Arbeitsbereich eines konkreten Stoffkits — Check three fixed-position gap measurements against the documented fabric kit range.

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": {
      "spalt_unten_mm": "<spalt_unten_mm>",
      "spalt_mitte_mm": "<spalt_mitte_mm>",
      "spalt_oben_mm": "<spalt_oben_mm>",
      "kit_min_mm": "<kit_min_mm>",
      "kit_max_mm": "<kit_max_mm>"
    },
    "name": "dachfenster_oeffnung_spaltprofil_kitbereich"
  }
}

Input Schema

NameRequiredDescriptionDefault
kit_max_mmYesDokumentierter Höchstspalt dieses Kits in mm.
kit_min_mmYesDokumentierter Mindestspalt dieses Kits in mm.
spalt_oben_mmYesSpalt oben in mm.
spalt_mitte_mmYesSpalt mittig in mm.
spalt_unten_mmYesSpalt unten bei derselben Öffnungsstellung in mm.

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?

The annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the behavioral framing 'static/fixed-position' and 'documented range', but says nothing about what a comparison yields (pass/fail, which gap is out of range, tolerance handling), which matters since no output schema exists.

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 in German and English that states the operation first and the inputs second, with no filler. The bilingual duplication is slightly redundant but aids disambiguation of the domain terms.

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 five-number, fully documented, read-only comparison tool, the inputs are adequately covered. The notable gap is the result: with no output schema, the agent cannot tell whether the tool returns a boolean, a per-gap verdict, or the violating dimension, so the description should have closed that hole.

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 coverage is 100% and each parameter is already documented in German, including the note that the lower gap is measured 'bei derselben Öffnungsstellung'. The description only restates the shape of the input (three fixed gaps plus min/max range) without adding units, ordering, or validation semantics beyond the schema.

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 three fixed-position gap measurements against a kit's documented range) and specifies the scope: 'static' gap values versus 'declared' kit limits. It is specific enough to distinguish from dynamic/multi-reading siblings, though it does not name any sibling it competes with.

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 explicit statement of when to use this versus alternatives such as the kit-acceptance or edge-reserve siblings. The purpose implies a conformance check, but exclusions, prerequisites, and the choice among similar kit tools are left entirely to inference.

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