Skip to main content
Glama

getecoback-raumklima

tuerventilator_raumgefaelle_versuch

Read-only

Vergleicht Temperaturgefälle zwischen zwei Räumen mit und ohne aktiven Türventilator — Compare observed room-temperature gaps with and without a doorway fan.

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": {
      "nebenraum_ohne_c": "<nebenraum_ohne_c>",
      "zielraum_ohne_c": "<zielraum_ohne_c>",
      "nebenraum_mit_c": "<nebenraum_mit_c>",
      "zielraum_mit_c": "<zielraum_mit_c>",
      "startwerte_und_dauer_vergleichbar": "<startwerte_und_dauer_vergleichbar>"
    },
    "name": "tuerventilator_raumgefaelle_versuch"
  }
}

Input Schema

NameRequiredDescriptionDefault
zielraum_mit_cYesTemperatur Zielraum am Ende mit Ventilator in °C.
nebenraum_mit_cYesTemperatur Nebenraum am Ende mit Ventilator in °C.
zielraum_ohne_cYesTemperatur Zielraum am Ende ohne Ventilator in °C.
nebenraum_ohne_cYesTemperatur Nebenraum am Ende ohne Ventilator in °C.
startwerte_und_dauer_vergleichbarYesWaren Starttemperaturen, Öffnungen sowie Messdauer beider Versuche vergleichbar?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 and the bar is lower. Beyond that, the description adds nothing behavioral: it never says what the tool returns (a delta, a verdict, a corrected comparison) or how 'startwerte_und_dauer_vergleichbar'=false alters the result, which is the one behavior an agent most needs to know.

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 that states the comparison subject immediately, with a bilingual restatement that aids matching but is technically redundant. No filler or hedging.

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?

A pure computation tool with five required parameters and no output schema needs the description to say what comes back and how the comparability boolean gates the answer; neither is covered. The result format is left entirely to inference, which is a real gap for a calculator-style tool.

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%, with units (°C), bounds (-30 to 70) and role of each of the five parameters documented in the schema. The description adds no meaning beyond that, so the baseline 3 applies.

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 concrete verb and resource ('Vergleicht Temperaturgefälle zwischen zwei Räumen mit und ohne aktiven Türventilator'), so an agent can tell this is a fan-vs-no-fan temperature-gap comparison. It does not distinguish itself from near siblings such as feuchte_versuch_referenzraum, and it leaves implicit that the tool computes the comparison from supplied readings rather than retrieving measurements.

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?

No when-to-use condition, prerequisite, or alternative is stated. The agent must infer from the parameter names alone that this is for post-experiment comparison of two paired trials; there is no guidance on when to prefer this over other experiment-evaluation siblings or what to do when the comparability flag is false.

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