Skip to main content
Glama

getecoback-raumklima

klima_testbedingungen_verbundflaeche_messorte

Read-only

Vergleiche die gemeldete Kühl-Abdeckung bei offener Tür mit der tatsächlich dokumentierten Raumgruppe — Scope a cooling test claim to the rooms actually observed

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": {
      "getestete_hauptflaeche_m2": "<getestete_hauptflaeche_m2>",
      "verbundflaeche_m2": "<verbundflaeche_m2>",
      "verbund_beobachtet_m2": "<verbund_beobachtet_m2>",
      "messziel_und_tueren_belegt": "<messziel_und_tueren_belegt>"
    },
    "name": "klima_testbedingungen_verbundflaeche_messorte"
  }
}

Input Schema

NameRequiredDescriptionDefault
verbundflaeche_m2YesZusätzliche Grundfläche, die der Bericht als verbunden nennt
verbund_beobachtet_m2YesDavon zusätzliche Fläche, für die Ziel und Messorte nachvollziehbar protokolliert wurden
getestete_hauptflaeche_m2YesGrundfläche des im Test direkt beobachteten Raums
messziel_und_tueren_belegtYesZiel, Türen und Position der Messpunkte sind im Bericht dokumentiert

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 safety profile is covered and the description is not contradicting anything. It adds the useful framing that this is a claim-scoping comparison tied to open-door cooling coverage, but says nothing about how mismatched inputs are handled (e.g. observed area exceeding claimed area) or what the result looks like. With annotations carrying the read-only story, this is adequate but thin.

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 the subject (cooling coverage claim) front-loaded before the qualifying clause. The bilingual restatement is somewhat redundant but short enough that it functions as clarification rather than padding.

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 pure computation tool with no output schema, the description should indicate what the computed result represents, and it does not. Parameter documentation and annotations are complete, so the agent can supply inputs, but it cannot predict the return value before calling.

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 self-documenting and the baseline is 3. The description hints at the semantics behind the split between claimed linked area and actually observed area ("Raumgruppe", "rooms actually observed"), but it does not explicitly map any parameter to its role in the comparison, so it adds only marginal meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Vergleiche die gemeldete Kühl-Abdeckung bei offener Tür mit der tatsächlich dokumentierten Raumgruppe" names a verb (compare) and the resources being compared, and the English gloss "Scope a cooling test claim to the rooms actually observed" adds the intent. But it never states what the comparison produces (a ratio, a pass/fail, a corrected coverage figure), and no sibling tool is named to differentiate it from the many other klima_* checks.

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 alternative tool is mentioned. The phrase "Scope a cooling test claim" only weakly implies the situation in which it applies, leaving the agent to infer the trigger condition from the sibling catalog.

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