Skip to main content
Glama

getecoback-climate-weather

heizfuehler_standort

Read-only

Platz eines Raumtemperaturfühlers auf typische Messfehler prüfen — Check placement of a room sensor for heat, draught and obstructions.

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": {
      "near_heat_or_sun": "<near_heat_or_sun>",
      "in_draught": "<in_draught>",
      "covered": "<covered>"
    },
    "name": "heizfuehler_standort"
  }
}

Input Schema

NameRequiredDescriptionDefault
coveredYesIst der Fühler durch Möbel oder Vorhänge abgeschirmt?
in_draughtYesWird der Fühler regelmäßig durch Zugluft abgekühlt?
near_heat_or_sunYesIst der Fühler nahe einer Wärmequelle, direkter Sonne oder Wärmestrahlung?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. Beyond that, the description discloses almost nothing about behavior: it does not say what the check produces (a verdict, a list of flagged issues, recommendations), how the three inputs are combined, or what an all-false result means. For a tool with no output schema, that is a meaningful gap.

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?

One front-loaded sentence with zero filler; the core action comes first. The German and English variants are duplicative, which is mild redundancy rather than waste, so it falls just short of a 5.

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 three required booleans, no nesting, and no output schema, the definition is minimally sufficient to invoke the tool. However, it never indicates what the agent receives back or how to interpret or act on the result, which is the main thing a diagnostic tool's description should cover.

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 each of the three booleans has a precise German description explaining the condition. The description's parenthetical (heat, draught, obstructions) merely restates those parameters, adding no syntax, threshold, or interpretation guidance beyond the schema. 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?

"Platz eines Raumtemperaturfühlers auf typische Messfehler prüfen" names a specific verb (prüfen/check) and resource (sensor placement) and enumerates the three failure modes examined (heat, draught, obstructions). It is clearly distinct from siblings like heizkoerper_kalt_pruefen or hygrometer_messbereiche, though it never names an alternative directly.

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?

Usage is only implied: the phrase "typische Messfehler" suggests the tool is for diagnosing suspect room-temperature readings, but there is no explicit when-to-use statement, no prerequisites, and no routing away from related checks such as draught or hygrometer tools. An agent must infer the context itself.

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