Skip to main content
Glama

getecoback-raumklima

beurer_lr401_raumflaechenangabe_hoehenbezug

Read-only

Rechne die LR-401-Flächenangabe in ihr geometrisches Bezugsvolumen um — Interpret the LR 401 published area at its documented ceiling height

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": {
      "lr401_68013": "<lr401_68013>",
      "hersteller_flaeche_m2": "<hersteller_flaeche_m2>",
      "wohnungshoehe_m": "<wohnungshoehe_m>",
      "wohnungsflaeche_m2": "<wohnungsflaeche_m2>"
    },
    "name": "beurer_lr401_raumflaechenangabe_hoehenbezug"
  }
}

Input Schema

NameRequiredDescriptionDefault
lr401_68013YesBeurer LR 401, Artikel 68013, anhand der deutschen Herstellerunterlage bestätigt
wohnungshoehe_mYesMittlere Höhe des gemessenen Raums in Metern
wohnungsflaeche_m2YesGemessene Grundfläche dieses Raums
hersteller_flaeche_m2YesVom Hersteller für 2,4 m Deckenhöhe genannte Vergleichsfläche

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/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 the safety profile is covered by structured data rather than the text. The description adds nothing beyond that: it does not say how the height scaling is performed, what happens when the measured height diverges from the documented ceiling height, or what the required confirmation flag actually gates.

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 short clauses, front-loaded with the action, with no filler sentences. The German/English duplication is slightly redundant but serves as a gloss for an unusual domain term rather than padding.

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?

For a four-parameter calculation tool with no output schema, the description should explain the computation and the returned quantity, and it does neither. The role of the mandatory confirmation boolean and the interaction between manufacturer area, measured area, and height are left entirely to inference.

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 the schema, including the 2.4 m manufacturer reference height. The description only adds the notion of interpreting the manufacturer area 'at its documented ceiling height', which is marginal extra meaning over what the schema already states; baseline 3 applies.

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 transform (LR-401 published area -> geometric reference volume) at a documented ceiling height, which is more than a restatement of the name. However, the jargon 'geometrisches Bezugsvolumen' is never grounded in the actual quantities in the schema (measured room area, room height, manufacturer comparison area), so an agent cannot tell precisely what is being computed from what.

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 statement of when this tool applies versus any other conversion or comparison tool, and no prerequisites are given. The required boolean lr401_68013 implies a confirmation gate based on German manufacturer documentation, but the description never says that the tool should only be used once that confirmation holds.

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