Skip to main content
Glama

getecoback-raumklima

monoblock_auslass_freiraum_beobachtungsbeleg

Read-only

Vergleicht gemessenen Freiraum am Auslass mit der ausdrücklich dafür dokumentierten Vorgabe — Compare measured clearance at the outlet with its documented requirement.

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": {
      "soll_mm": "<soll_mm>",
      "sichtbar_frei_mm": "<sichtbar_frei_mm>",
      "gleiche_richtung": "<gleiche_richtung>",
      "abstand_belegt": "<abstand_belegt>"
    },
    "name": "monoblock_auslass_freiraum_beobachtungsbeleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
soll_mmYesAusdrückliche Mindestvorgabe genau für den Auslass dieses Modells in mm.
abstand_belegtYesLiegt der gemessene Abstand ohne Schätzung verdeckter Bereiche vor?
gleiche_richtungYesSind Bezugsfläche, Richtung und Gerätemodus identisch?
sichtbar_frei_mmYesBereits gefahrlos bemaßter freier Abstand in der vorgegebenen Richtung 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 readOnlyHint=true and openWorldHint=false annotations already establish this as a closed-world, non-mutating check, and the description is consistent with that ('Vergleicht'). It adds one meaningful qualifier — that the requirement must be the one expressly documented for this outlet — but says nothing about the nature of the result, whether a tolerance applies, or what happens on mismatch.

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 that states the comparison before its qualifier, with no filler. The German/English duplication costs some length, though it aids matching against the German tool name and parameters.

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-parameter, fully documented, read-only check the definition is serviceable, but with no output schema it never indicates what the tool returns or how a comparison result should be read. The two boolean guard parameters (gleiche_richtung, abstand_belegt) imply gating logic that the description does not explain.

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 (soll_mm, sichtbar_frei_mm, gleiche_richtung, abstand_belegt) are already documented with bounds and intent. The description's measured-vs-documented framing loosely maps onto sichtbar_frei_mm vs soll_mm but adds no format, unit, or edge-case meaning 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 names a specific operation (compare measured outlet clearance against the documented requirement) and a specific object (Freiraum am Auslass), so the agent knows this is an evaluation/verdict tool rather than a measurement or lookup tool. It does not explicitly differentiate itself from near-neighbours such as dachfenster_auslass_sichtgrenze_von_innen, leaving that distinction to be inferred from the resource name.

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 or when-not-to-use guidance and no named alternative. The agent must infer from the wording that this applies only when an explicitly documented requirement exists for that exact outlet, and nothing tells it what to do when the requirement is missing or estimated.

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