Skip to main content
Glama

getecoback-raumklima

arbeitsplatz_fusshoehe_sitzhoehe_wiederkehrmuster

Read-only

Am selben Schreibtisch wiederholt kühle Fußzone von durchgängig kühler Sitzluft unterscheiden — Classify a repeated colder foot-zone observation separately from a whole-seat drop.

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_fuss_c": "<a_fuss_c>",
      "a_sitz_c": "<a_sitz_c>",
      "b_fuss_c": "<b_fuss_c>",
      "b_sitz_c": "<b_sitz_c>",
      "differenz_relevant_k": "<differenz_relevant_k>",
      "aufbau_wiederholt": "<aufbau_wiederholt>"
    },
    "name": "arbeitsplatz_fusshoehe_sitzhoehe_wiederkehrmuster"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_fuss_cYesErste Messung auf Fußhöhe.
a_sitz_cYesErster zeitgleicher Messwert auf Sitzhöhe.
b_fuss_cYesSpätere Messung an genau demselben Fußpunkt.
b_sitz_cYesZweiter zeitgleicher Wert auf Sitzhöhe.
aufbau_wiederholtYesMessorte, Gerät und Versuchsaufbau blieben gleich.
differenz_relevant_kYesEigene Mindestdifferenz für diese Messung, in K.

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 declare readOnlyHint=true and openWorldHint=false, so the safety profile is already covered. The description adds that the tool performs a comparative classification across two timepoints at foot and seat height, which is useful behavior beyond the annotations, but it says nothing about the form of the classification result, especially important since there is no output schema.

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?

The definition is a single compact sentence pair with the key distinction front-loaded and no filler. The bilingual restatement is mildly redundant but does aid comprehension rather than padding the text.

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 six required numeric/boolean parameters and no output schema, the description should convey what the classification returns and how the threshold parameter shapes it. It conveys the intent of the comparison but leaves the result shape and threshold interaction to inference, which is a meaningful gap for a tool whose whole output is a classification verdict.

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 six parameters are fully documented in structured form and the baseline is 3. The description implicitly ties the comparison to the foot-vs-seat pairs and the same-setup repeat condition, but adds no syntax, units, or thresholds beyond what the schema already states.

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 concrete task: classifying a repeated colder foot-zone observation separately from a whole-seat temperature drop, tied to measurements at the same desk. It is specific about the distinction being drawn, though the distinction is conceptual rather than a named sibling tool, and the German/English duplication makes the core verb ('unterscheiden' / 'Classify') slightly less crisp.

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?

'Am selben Schreibtisch wiederholt' implies the precondition of repeated measurement under an unchanged setup, which is real usage context. However, no explicit when-not conditions or alternative tools are named, and the agent must infer from the parameter set that two paired timepoint measurements are required.

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