Skip to main content
Glama

getecoback-climate-weather

innenrollo_lichtspalt_pruefen

Read-only

Die Stofffläche eines Klemmrollos mit der Glasfläche vergleichen — Check side light gaps using cloth width rather than mounting-bracket width.

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": {
      "glas_cm": "<glas_cm>",
      "stoff_cm": "<stoff_cm>",
      "gesamt_cm": "<gesamt_cm>",
      "montagezone_cm": "<montagezone_cm>"
    },
    "name": "innenrollo_lichtspalt_pruefen"
  }
}

Input Schema

NameRequiredDescriptionDefault
glas_cmYesSichtbare Glasbreite.
stoff_cmYesTatsächliche Stoffbreite laut genauem Modell.
gesamt_cmYesGesamtbreite des Rollos inklusive Haltern.
montagezone_cmYesNutzbare Breite für die Halter ohne Griffe und Kollisionen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 the agent knows this is a safe, closed-world evaluation and the description needn't re-establish that. What the description does add is the comparison model (cloth surface vs. glass surface) and which width basis to trust. It does not say what the check returns or how a gap verdict is expressed, which is a real gap for a verification 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 front-loaded clauses with the operational distinction placed after the purpose, so the agent reads the what before the how. The German and English halves are near-duplicates, which costs a little space but aids bilingual robustness rather than adding noise.

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 four-required-numeric-parameter computation with no output schema, the description covers the comparison inputs but not the result semantics — whether it yields a gap measurement, a pass/fail, or a threshold comparison. It is adequate to start the call but leaves the agent guessing at the outcome shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3, but the description earns extra credit by telling the agent to prioritize stoff_cm over the bracket-inclusive gesamt_cm when evaluating the side gap — a precedence rule the four terse schema descriptions do not encode. It still leaves montagezone_cm's role in the comparison implicit.

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 action (checking side light gaps / comparing cloth surface against glass surface) for a specific product type (Klemmrollo), so the agent knows exactly what domain of check this performs. It also distinguishes the measurement basis (Stoffbreite, not Halterbreite), which is more than a restatement of the name. It stops short of a 5 because it never contrasts itself with any sibling check tool.

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?

Usage is implied rather than stated: the agent can infer this is the check to run when a clamp roller blind's side gap is in question. The 'cloth width rather than mounting-bracket width' clause is a methodological hint, not a when-to-use/when-not-to-use rule, and no alternative tool or preconditions are named.

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