Skip to main content
Glama

getecoback-raumklima

pc_ansaugluft_zu_raum_und_auslass

Read-only

Bei einem stationären PC gleichzeitig warmen Ansaugort und warmen Abluftbereich gegenüber dem fernen Raumwert dokumentieren — Distinguish three simultaneous PC observation points from a room-temperature claim.

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": {
      "raum_fern_c": "<raum_fern_c>",
      "ansaug_c": "<ansaug_c>",
      "auslass_c": "<auslass_c>",
      "unterscheidbar_c": "<unterscheidbar_c>",
      "messorte_getrennt": "<messorte_getrennt>"
    },
    "name": "pc_ansaugluft_zu_raum_und_auslass"
  }
}

Input Schema

NameRequiredDescriptionDefault
ansaug_cYesÄußerer Messwert an der Ansaugseite, ohne die Öffnung zu verdecken.
auslass_cYesÄußerer Messwert im gesonderten Auslassbereich.
raum_fern_cYesMöglichst unbeeinflusster zeitgleicher Raummesswert abseits des Arbeitsplatzes.
unterscheidbar_cYesVorab begründete kleinste unterscheidbare Temperaturdifferenz in K.
messorte_getrenntYesAlle drei Messorte und Zeiten sind eindeutig getrennt protokolliert.

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 already declare readOnlyHint=true and openWorldHint=false. The description reinforces read-only documentation and adds the simultaneity constraint, but it does not say whether values are stored, validated, or returned.

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?

Two sentences with the condition front-loaded, but the English sentence largely restates the German one and adds abstraction rather than operational detail.

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 tool with no output schema, the description gives the measurement scenario but omits what the tool returns or how recorded values are used. The detailed schema compensates partly, 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 coverage is 100%, so the five temperature/boolean parameters are already documented in the schema. The description only references the three observation points generally and adds no further meaning for unterscheidbar_c or messorte_getrennt.

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 uses a specific verb ('dokumentieren') and names the three observation points: intake location, exhaust area, and distant room value. It is clear enough to separate this from generic room-temperature tools, though it does not explicitly name a sibling alternative.

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?

It implies the setting (stationary PC with warm intake and exhaust compared to a distant room value) but does not state when to avoid this tool or which sibling to use for alternative measurement designs.

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