Skip to main content
Glama

getecoback-raumklima

heizmessung_warme_raumzone_vor_und_nach_sesselwechsel

Read-only

Prüfe, ob eine beobachtete kältere Sitzzone nach Umstellung auch in den Vergleichspunkten erhalten blieb — Test whether a colder seat zone persists after moving furniture

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_vor_c": "<a_vor_c>",
      "b_vor_c": "<b_vor_c>",
      "a_nach_c": "<a_nach_c>",
      "b_nach_c": "<b_nach_c>",
      "differenzgrenze_c": "<differenzgrenze_c>",
      "gleiche_heizphase": "<gleiche_heizphase>"
    },
    "name": "heizmessung_warme_raumzone_vor_und_nach_sesselwechsel"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_vor_cYesFrüherer Luftwert am festen Sitzpunkt A
b_vor_cYesGleichzeitiger früherer Wert am festen Punkt B
a_nach_cYesSpäterer Wert am unveränderten Punkt A
b_nach_cYesGleichzeitiger späterer Wert am unveränderten Punkt B
differenzgrenze_cYesSelbst festgelegter Mindestabstand, ab dem A deutlich kälter zählt
gleiche_heizphaseYesVergleichbare Heizphase, feste Messorte trotz umgestellter Sitzmöbel

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The read-only and closed-world annotations already establish the safety profile. The description adds the comparative test context, but it does not explain the return value, how the difference threshold is applied, or what happens when the heating-phase condition is false.

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?

It is a single front-loaded sentence with no filler. The bilingual repetition is slightly redundant but still compact and clear.

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?

For a six-parameter comparison tool with no output schema, the description explains the intended check but not what result is returned or how edge cases are handled. The schema carries most of the necessary detail, leaving this adequate but not complete.

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 are fully documented in the schema. The description adds contextual meaning about comparison points and persistence but no additional parameter-level syntax or constraints.

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 states a specific check: whether an observed colder seat zone remains at the comparison points after rearranging. It is clearer than the technical tool name alone, though it does not explicitly differentiate itself from any sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear usage context: after a furniture rearrangement, when a colder seat zone was observed. It does not provide exclusions or explicit alternatives, but the scenario is sufficiently clear for selection.

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