Skip to main content
Glama

getecoback-climate-weather

klima_abkuehltest_auswerten

Read-only

Temperaturverlauf bei einem kurzen Funktionstest auswerten — Summarize observed cooling from timed measurements at the same indoor location.

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>",
      "nachher_c": "<nachher_c>",
      "minuten": "<minuten>",
      "bedingungen_stabil": "<bedingungen_stabil>"
    },
    "name": "klima_abkuehltest_auswerten"
  }
}

Input Schema

NameRequiredDescriptionDefault
minutenYesDauer des beobachteten Tests in Minuten.
vorher_cYesTemperatur am gleichen Messort zu Testbeginn in °C.
nachher_cYesTemperatur am gleichen Messort zu Testende in °C.
bedingungen_stabilYesSonne, Türen, Belegung und andere Einflüsse blieben hinreichend ähnlich?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so this is a safe, closed-domain computation; the description's job is to say what it produces, and 'Summarize observed cooling from timed measurements' does that (a summary, not a diagnosis or recommendation). It does not disclose how the required 'bedingungen_stabil' flag affects the result, which is the one behavioral gap.

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 front-loaded sentence stating purpose first, then the measurement conditions. The German plus English restatement is mildly redundant, but the sentence carries no filler beyond that duplication.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A four-required-parameter, read-only computation with no output schema; the description names the input semantics (same location, timed, short test) and the nature of the return value (a summary of observed cooling). Only the treatment of the stability flag is left unexplained, a minor omission for a tool this simple.

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 coverage is 100% and every parameter carries its own German description, so the schema does the heavy lifting. The description reinforces the key constraint that both readings must come from the same indoor location but adds no units, ranges, or interpretation guidance beyond that — baseline 3 is 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 gives a specific verb (auswerten/summarize) and resource (Temperaturverlauf / beobachtete Abkühlung), plus qualifying scope: 'kurzer Funktionstest' and 'am gleichen Messort'. That is well beyond tautology, though it never differentiates from the many other klima_* tools, so a 4 rather than a 5.

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?

Use context is implied by 'bei einem kurzen Funktionstest' and 'timed measurements at the same indoor location' — the agent can infer this is for short functional checks, not long-term monitoring. But there is no explicit when-not guidance, no named alternative, and no statement about what to do when conditions were not stable.

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