Skip to main content
Glama

getecoback-raumklima

punktwaerme_verdeckter_unterschied_koerperzonen

Read-only

Eine Gesamtbeurteilung auf gegenläufige persönliche Wärmeeindrücke an Händen und Füßen prüfen — Retain oppositely changing body-zone comfort instead of averaging it into one result.

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": {
      "haende_vorher": "<haende_vorher>",
      "fuesse_vorher": "<fuesse_vorher>",
      "haende_nachher": "<haende_nachher>",
      "fuesse_nachher": "<fuesse_nachher>",
      "selbe_aufgabe": "<selbe_aufgabe>"
    },
    "name": "punktwaerme_verdeckter_unterschied_koerperzonen"
  }
}

Input Schema

NameRequiredDescriptionDefault
fuesse_vorherYesBeobachtung ohne Zusatzwärme an den Füßen.
haende_vorherYesBeobachtung ohne Zusatzwärme an den Händen.
selbe_aufgabeYesVergleichbare Aktivität, Kleidung und Bewertungsweise?
fuesse_nachherYesBeobachtung im Vergleichsversuch an den Füßen.
haende_nachherYesBeobachtung im Vergleichsversuch an den Händen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 the safety profile is covered. The description does add one behavioral trait beyond that: it retains the divergence rather than collapsing it, which tells the agent something about the result semantics. It still says nothing about the response shape, and with no output schema that gap stays open.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core idea is front-loaded, but the German sentence and the English sentence are near-translations of each other, so roughly half the text is duplicative. Content that could earn its place instead, such as what the retained result looks like, is absent.

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 five-required-parameter, read-only evaluation tool with no output schema, the definition should say what the retained divergence is returned as and why all five observations must be supplied together. It conveys the intent but not the result contract, so it is adequate rather than 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% and four parameters carry enums with per-field descriptions, so the schema already does the heavy lifting. The description refers only generically to hands and feet and adds no meaning about the before/after pairing or the role of 'selbe_aufgabe' as a validity gate. 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 names a specific operation: checking an overall judgement for counter-directional warmth impressions at hands versus feet, and explicitly contrasts it with averaging into one result. That contrast implicitly separates it from the aggregate/zone-distribution siblings. It stops short of naming an actual alternative tool, so it is clear but not fully differentiating.

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 phrase 'gegenläufige persönliche Wärmeeindrücke' and 'instead of averaging' implies the situation in which to use it (opposite-direction hand/foot observations). However, there is no explicit when-not guidance, no prerequisites, and no named alternative for the averaging case, leaving the routing decision partly to inference.

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