Skip to main content
Glama

getecoback-climate-weather

dunstabzug_umluft_und_fensterprogramm_zuordnung

Read-only

Trenne einen gemessenen oder angegebenen Umluftstrom der Haube vom getrennt nachgewiesenen Außenbezug — Keep cooker-hood recirculation apart from independently documented outdoor airflow

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": {
      "haubenmodus": "<haubenmodus>",
      "haubenwert_m3_h": "<haubenwert_m3_h>",
      "aussen_zusatz_m3_h": "<aussen_zusatz_m3_h>",
      "aussen_zusatz_belegt": "<aussen_zusatz_belegt>"
    },
    "name": "dunstabzug_umluft_und_fensterprogramm_zuordnung"
  }
}

Input Schema

NameRequiredDescriptionDefault
haubenmodusYesVorgang laut eigener Beobachtung oder Modellunterlage
haubenwert_m3_hYesFür diese Betriebsart dokumentierter Haubenwert in m³/h
aussen_zusatz_m3_hYesSeparat belegter, zeitgleich beobachteter Außenluftvolumenstrom in m³/h
aussen_zusatz_belegtYesSeparater Außenweg, gleiche Bezugszeit und keine Doppelzählung bestätigt

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the operation is a separation between recirculation and independently documented outdoor airflow, but it does not explain the result, validation behavior, or how the separation is represented.

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 definition is a single front-loaded sentence with no filler and the verb appears immediately. The German-English duplication is somewhat redundant, but the overall wording is compact and readable.

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?

For a tool with four required parameters and no output schema, the one-sentence description does not explain what the tool returns or how the resulting separation should be interpreted. The schema covers inputs and the annotations cover safety, but the result semantics are missing.

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 documents all four required parameters in detail. The description reinforces the distinction between measured/specified recirculation airflow and separately documented outdoor airflow, but it adds no enum, unit, format, or constraint detail beyond what the schema provides.

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 gives a specific verb, 'Trenne' (separate), and names the two resources being kept apart: the hood's recirculation airflow and the independently documented outdoor airflow. It does not name a sibling alternative, and the 'Fensterprogramm' element in the tool name is not explained, but the core operation is identifiable.

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?

The description implies the scenario of separating measured or specified recirculation airflow from separately documented outdoor airflow, but it never states when an agent should choose this tool over the many dunstabzug_* sibling assignment tools. No exclusions, prerequisites, or alternative tools are mentioned.

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