Skip to main content
Glama

getecoback-climate-weather

klimafenster_platte_nennlaenge_hub

Read-only

Vergleiche eine dokumentierte Teleskopspanne mit den Öffnungsmaßen eines Schiebefensters — Compare a sliding-window insert range with the actual opening

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_oeffnung_mm": "<lichte_oeffnung_mm>",
      "minimale_platte_mm": "<minimale_platte_mm>",
      "maximale_platte_mm": "<maximale_platte_mm>",
      "bauart_belegt": "<bauart_belegt>"
    },
    "name": "klimafenster_platte_nennlaenge_hub"
  }
}

Input Schema

NameRequiredDescriptionDefault
bauart_belegtYesDas Zubehör nennt die vorhandene Schiebefenster-Bauart
lichte_oeffnung_mmYesLichte Öffnung entlang der Verstellrichtung
maximale_platte_mmYesGrößte Einbaulänge laut Zeichnung
minimale_platte_mmYesKleinste Einbaulänge laut Zeichnung

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/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. However, the description adds no behavioral context: it does not say what the comparison yields, how a mismatch is reported, or what role the 'bauart_belegt' flag plays. With no output schema, this is a notable gap for a verdict-producing check tool.

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?

Two short sentences, front-loaded with the core comparison, and no filler. The only cost is that brevity leaves the outcome semantics unexplained.

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?

There is no output schema, yet the description never explains what the comparison produces or how the 'bauart_belegt' boolean affects the result. For a four-required-parameter validation tool, the definition is under-specified about outcomes.

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 with units, bounds, and meaning. The description adds no interpretation beyond the schema, so the baseline of 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?

The description states a specific verb and resource: comparing a documented telescoping/insert range ('Teleskopspanne') against the clear opening dimensions of a sliding window. The bilingual restatement reinforces the same meaning. It is clear what the tool does, though it does not name or contrast any sibling.

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 when-to-use guidance, no prerequisites, and no mention of when this check should be skipped or which alternative applies. The agent has to infer from the name alone that this is a fit/range validation tool.

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