Skip to main content
Glama

getecoback-raumklima

hygrometer_messort_pruefen

Read-only

Messort für einen vergleichbaren Raumwert auswählen — Check whether hygrometer placement is suitable for tracking room-air humidity.

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": {
      "in_direct_sun_or_heat": "<in_direct_sun_or_heat>",
      "near_window_or_cold_wall": "<near_window_or_cold_wall>",
      "near_moisture_source": "<near_moisture_source>"
    },
    "name": "hygrometer_messort_pruefen"
  }
}

Input Schema

NameRequiredDescriptionDefault
near_moisture_sourceYesDirekt bei Dusche, Wäsche oder anderem Feuchteeintrag?
in_direct_sun_or_heatYesDirekte Sonne oder nah an Heizkörper beziehungsweise Wärmequelle?
near_window_or_cold_wallYesDirekt am Fenster oder an einer kalten Wand?

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 confirms that the tool is a placement check, but it does not explain how the three conditions are evaluated, what verdict or recommendation is returned, or what happens when multiple flags are true. It adds only minimal context beyond the annotations.

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 description is short, but it repeats the same content in German and English without adding information. It is front-loaded adequately, but the duplicated sentence does not fully earn its place.

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 simple read-only three-boolean check with no output schema, the description should explain what result the check produces, for example a suitability verdict and the reason for it. It says what is checked but not what an agent gets back, leaving a gap an agent must infer.

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 each boolean already carries a clear German explanation of the condition it represents. The description adds no meaning beyond the schema, gaining no extra credit, but it also does not need to. The baseline of 3 is appropriate.

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 verb and resource: selecting a measuring location and checking whether hygrometer placement is suitable for tracking room-air humidity. This distinguishes it from the sibling hygrometer_messbereiche, which covers measuring ranges rather than placement. The bilingual phrasing is slightly redundant but the purpose remains clear.

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 'Messort für einen vergleichbaren Raumwert auswählen' implies the tool is used when choosing a comparable measurement spot, but there is no explicit when-to-use guidance, no prerequisites, and no named alternatives or exclusions. Usage context is only implied.

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