Skip to main content
Glama

getecoback-raumklima

q350_tr_aufstellraum_messbereich_quellenabgleich

Read-only

Spiegelt den im Aufstellraum beobachteten Temperaturbereich gegen die exakt zugeordnete Dokumentgrenze — Check measured installation-room temperatures against the matched Q350 TR data limits.

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": {
      "min_c": "<min_c>",
      "max_c": "<max_c>",
      "innen_gemessen": "<innen_gemessen>",
      "v0126_passt": "<v0126_passt>"
    },
    "name": "q350_tr_aufstellraum_messbereich_quellenabgleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_cYesHöchster dokumentierter Wert im Aufstellraum in °C.
min_cYesTiefster dokumentierter Wert im tatsächlichen Aufstellraum in °C.
v0126_passtYesExakte deutsche Q350-TR-Ausführung und V0126-Angabe bestätigt.
innen_gemessenYesTatsächlich am vorgesehenen Aufstellort beobachtet, nicht Außenwetter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 safety and locality are covered. The description adds that the comparison is against the 'exakt zugeordnete Dokumentgrenze', i.e. a precisely matched limit rather than a rough one, which is useful context. It does not say what a failed check produces, whether mismatches are reported per bound, or what the response looks like, and no output schema fills that 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 stating the comparison before any detail, with zero preamble. The German and English halves are essentially the same statement twice, which is defensible in a bilingual catalog but is still duplication rather than added information.

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 four-parameter, fully-required, read-only validation tool with no output schema, the definition covers what is being compared but not what the comparison yields or how a mismatch is surfaced. The precondition implied by v0126_passt is left implicit. An agent could invoke it correctly, but not predict or interpret the result well.

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%, with all four required parameters documented in German (min_c, max_c, innen_gemessen, v0126_passt), so the baseline is 3. The description reinforces that min_c/max_c are the observed range and that the counterpart is a document limit, but it adds nothing about the semantics of the two boolean confirmation flags beyond what the schema already says.

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 concrete verb-and-resource pair: it mirrors/checks the observed temperature range in the installation room against the matched document limit. A reader can tell this is a comparison/validation tool rather than a lookup or filter tool. It does not name any sibling explicitly, so differentiation from the many q350_tr_* tools rests only on the 'check measured vs. limit' framing.

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 implied by the phrase 'Check measured installation-room temperatures against the matched Q350 TR data limits', which signals the situation in which it applies. There is no statement of when not to use it, no prerequisites (the required v0126_passt confirmation flag hints at a precondition but is never explained), and no named alternative among the sibling q350_tr_* 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