Skip to main content
Glama

getecoback-raumklima

sommerlueftung_abkuehlrate_nach_fensterschluss

Read-only

Prüfe, wie sich der Temperaturtrend zwischen Öffnung und dokumentiertem Schließen verändert — Compare cooling rates before and after closing a window

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": {
      "vorher_c": "<vorher_c>",
      "schluss_c": "<schluss_c>",
      "danach_c": "<danach_c>",
      "fenster_offen_min": "<fenster_offen_min>",
      "danach_min": "<danach_min>",
      "gleiche_randbedingungen": "<gleiche_randbedingungen>"
    },
    "name": "sommerlueftung_abkuehlrate_nach_fensterschluss"
  }
}

Input Schema

NameRequiredDescriptionDefault
danach_cYesRaumwert zur späteren Ablesung im geschlossenen Raum
vorher_cYesRaumwert direkt vor dem Öffnen
schluss_cYesRaumwert am selben Punkt zum Schließen
danach_minYesMinuten vom Schließen bis zur späteren Ablesung
fenster_offen_minYesGemessene Öffnungsdauer
gleiche_randbedingungenYesMesspunkt unverändert; äußere Bedingungen und andere Wärmequellen ähnlich

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, so safety is covered. The description adds only the comparative intent; it says nothing about what the result looks like (delta, classification, trend verdict) or what happens when the 'gleiche_randbedingungen' precondition is false. With annotations present the bar is lower, so a 3 is fair.

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 key concept front-loaded and a concise English gloss. The bilingual duplication costs a little space but adds no clutter or filler.

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?

All inputs are required and fully documented, and annotations establish it as a safe local computation. However, with no output schema, the description leaves the return value entirely unspecified for a six-parameter analytical tool, which is a meaningful gap for an agent deciding whether to call it.

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 six parameters (vorher_c, schluss_c, danach_c, fenster_offen_min, danach_min, gleiche_randbedingungen) already carry meaning. The description contributes no additional semantics about units, measurement points, or how the parameters combine, which is acceptable at baseline 3.

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: comparing the temperature trend/cooling rate before and after a documented window close, with the bilingual gloss making the intent unambiguous. It is clear what is computed, but it does not differentiate itself from closely related siblings such as nachtlueftung_temperaturruecklauf_nach_schliessen.

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 verb 'Prüfe' and the framing around 'Öffnung und dokumentiertem Schließen' imply the scenario in which to use it (post-close evaluation with before/after readings), but there is no explicit when-to-use/when-not-to-use statement and no alternative named.

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