Skip to main content
Glama

getecoback-raumklima

lueftungsverlauf_co2_minimum_gegen_temperaturgrenze

Read-only

Prüfe, ob das niedrigste erfasste CO₂ zum gleichen Zeitpunkt wie eine passende Raumtemperatur auftrat — Match the lowest recorded CO₂ reading with simultaneous temperature

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": {
      "a_ppm": "<a_ppm>",
      "a_c": "<a_c>",
      "b_ppm": "<b_ppm>",
      "b_c": "<b_c>",
      "temperaturziel_c": "<temperaturziel_c>",
      "simultan_bestaetigt": "<simultan_bestaetigt>"
    },
    "name": "lueftungsverlauf_co2_minimum_gegen_temperaturgrenze"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_cYesZeitgleiche Innenlufttemperatur A
b_cYesZeitgleiche Innenlufttemperatur B
a_ppmYesErste CO₂-Ablesung
b_ppmYesZweite CO₂-Ablesung
temperaturziel_cYesSelbst gewählte untere Temperaturgrenze
simultan_bestaetigtYesJedes Messpaar ist zeitlich und räumlich vergleichbar

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds nothing behavioral on top. It does not explain what happens when simultan_bestaetigt is false, how temperaturziel_c gates the result, or what the response looks like for a tool with no output schema. The bilingual duplication consumes space without adding disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Short and front-loaded, but the German sentence and the English sentence say the same thing, so roughly half the text is redundant. No wasted length, but also no added structure such as inputs-to-outcome framing.

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?

With 6 required parameters, no output schema, and a comparison-shaped purpose, the definition should at minimum explain the gating role of simultan_bestaetigt and the meaning of the temperaturziel_c threshold. Those gaps leave the agent able to call the tool but unsure how to interpret the result.

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 baseline is 3. The description only implies that the lowest of a_ppm/b_ppm is selected and that temperature comparability matters; it never explains how temperaturziel_c is applied as a lower bound or why simultan_bestaetigt is required, so it does not meaningfully extend 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?

The description names a recognizable operation — match the lowest recorded CO₂ reading against a simultaneous room temperature — but the compound German name plus a near-verbatim English echo do more restating than clarifying. It never says what the check produces (a boolean verdict, a matched pair, a pass/fail against temperaturziel_c), so an agent knows the topic but not the outcome.

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 guidance on when this check should be run instead of a sibling comparison tool, no prerequisites, and no exclusions. The agent must infer the use case entirely from the name and the parameter list.

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