Skip to main content
Glama

getecoback-climate-weather

hygrometer_anzeige_vom_sitzplatz

Read-only

Zwei Displayhöhen anhand des tatsächlichen Sitzplatzes vergleichen — Compare two hygrometer display positions from the usual reading seat.

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": {
      "augenhoehe_cm": "<augenhoehe_cm>",
      "waagerechter_abstand_cm": "<waagerechter_abstand_cm>",
      "display_a_cm": "<display_a_cm>",
      "display_b_cm": "<display_b_cm>"
    },
    "name": "hygrometer_anzeige_vom_sitzplatz"
  }
}

Input Schema

NameRequiredDescriptionDefault
display_a_cmYesHöhe der Anzeigemitte bei Position A in cm.
display_b_cmYesHöhe der Anzeigemitte bei Position B in cm.
augenhoehe_cmYesAugenhöhe am üblichen Sitzplatz in cm.
waagerechter_abstand_cmYesWaagerechter Abstand zum Display in beiden Positionen in cm.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already indicate this is read-only and closed-world, and the description does not contradict that. Beyond the annotations, however, it adds almost no behavioral context: it does not explain how the comparison is computed, what geometry or assumptions are used, or what kind of result the agent should expect.

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 definition is short and front-loaded, but it is simply the German sentence repeated in English. The duplication does not add information, and the wording remains too sparse to justify the space it consumes.

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?

This is a four-parameter computation tool with no output schema, so the description should explain what the comparison yields and how the seated eye height and distance are used. Instead it only restates the high-level idea, leaving the agent unable to predict the result or verify that the inputs are sufficient.

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 four parameters are already documented in detail as heights and horizontal distance in centimeters. The description reinforces that the comparison uses the actual seat and two display positions, but does not add syntax, constraints, or interpretation beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific action and resource: comparing two hygrometer display heights from the actual seating position. However, it never says what the comparison produces — viewing angle, legibility, ergonomic verdict, or something else — so the purpose remains only partially clear.

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?

There is no explicit guidance about when this tool should be used instead of the many sibling hygrometer tools. The phrase 'usual reading seat' implies a personal viewing scenario, but no alternatives, prerequisites, or exclusion conditions are given.

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