Skip to main content
Glama

getecoback-climate-weather

klima_lueftung_aufgaben_uebergabe

Read-only

Beim Wechsel zur Umluftkühlung erkennen, ob für die Frischluftaufgabe ein eigener Plan bleibt — Identify missing outdoor-air provision after switching to recirculating cooling.

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": {
      "luftwechsel": "<luftwechsel>",
      "kuehlart": "<kuehlart>",
      "lueftungsprofil_geaendert": "<lueftungsprofil_geaendert>"
    },
    "name": "klima_lueftung_aufgaben_uebergabe"
  }
}

Input Schema

NameRequiredDescriptionDefault
kuehlartYesWas bestätigt die Anleitung zum Kühlgerät?
luftwechselYesWie ist der beabsichtigte Frischluftaustausch eingeplant?
lueftungsprofil_geaendertYesWird das bisherige Frischluftprofil beim Saisonwechsel reduziert oder beendet?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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, covering the safety profile. The description adds domain context about diagnosing missing outdoor-air provision, but it does not explain how the boolean/enum inputs affect the outcome or what the tool returns, leaving behavioral gaps.

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?

The description is a single, front-loaded sentence with the scenario stated first. The bilingual German/English gloss is somewhat redundant, but overall it is efficient and wastes little space.

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 3-parameter read-only check with no output schema, the description gives the purpose and trigger condition but omits what the tool returns or how the parameters combine to produce a result. It is adequate but leaves the agent guessing about output expectations and decision logic.

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 the schema already fully documents all three parameters with enum values and boolean meaning. The description provides no additional parameter semantics, making the baseline 3 appropriate.

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 diagnostic purpose: identifying missing outdoor-air provision when switching to recirculating cooling. It clearly conveys the resource and check, though it does not explicitly distinguish this tool from the many neighboring climate/ventilation checks.

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?

The phrase 'Beim Wechsel zur Umluftkühlung' implies a trigger condition for usage, giving some contextual guidance. However, there is no explicit when-not guidance or mention of alternative sibling tools, so the agent must infer the boundaries.

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