Skip to main content
Glama

getecoback-climate-weather

heizzone_moebel_nutzungsstellung_abstand

Read-only

Zwei Möbelstellungen am Heizkörper auf den bestätigten Freiraum prüfen — Compare everyday and guest furniture positions against your documented clearance.

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": {
      "mindestabstand_cm": "<mindestabstand_cm>",
      "alltag_cm": "<alltag_cm>",
      "besuch_cm": "<besuch_cm>",
      "mindestabstand_belegt": "<mindestabstand_belegt>"
    },
    "name": "heizzone_moebel_nutzungsstellung_abstand"
  }
}

Input Schema

NameRequiredDescriptionDefault
alltag_cmYesKleinster dort gemessener Abstand in Alltagsstellung.
besuch_cmYesKleinster dort gemessener Abstand mit ausgeklapptem oder umgestelltem Möbel.
mindestabstand_cmYesBestätigte freie Distanz an der konkret geprüften Stelle.
mindestabstand_belegtYesPasst die Vorgabe zu genau diesem Heizkörper und der gemessenen Stelle?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 and the description does not contradict it. The description adds that the comparison is made against a pre-confirmed clearance at a specific radiator location, which is real context. It fails to state what the comparison yields (pass/fail per position, whether any furniture position violates the minimum), so with no output schema this remains a notable 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?

A single front-loaded sentence that states the operation and the comparison basis with no filler. The German/English duplication adds length but serves cross-language clarity, so it is not wasteful enough to drop below 4.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, four-required-parameter check with full schema coverage, the description supplies enough to call it correctly: which two distances are compared and against which confirmed clearance. It is missing only what the tool returns (the outcome of the comparison), which is the main remaining gap and costs it a point.

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 (everyday distance, guest distance, confirmed minimum, and whether the minimum applies to this exact radiator). The description adds only the framing that two positions are compared against the confirmed clearance, which is already implied by parameter names. Baseline 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?

Specific verb+resource: it checks two furniture positions (everyday vs. guest) at a radiator against a confirmed clearance. An agent can tell this is a clearance-comparison check rather than a general heater or scheduling tool. It does not name or distinguish itself from any sibling, so it stops short of a 5.

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 phrasing 'auf den bestätigten Freiraum prüfen' and 'against your documented clearance' implies the usage context (validating measured clearances against a confirmed specification). However, there is no explicit when-to-use/when-not guidance and no mention of alternatives such as the sibling comfort-band or clearance tools.

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