Skip to main content
Glama

getecoback-raumklima

wohnmessung_feste_referenz_zwei_rotationsorte

Read-only

Mit einem festen Referenzgerät und einem umgesetzten Gerät zwei Raumvergleiche zeitlich absichern — Check simultaneous coverage for a fixed logger and two rotating rooms.

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": {
      "ref_ab": "<ref_ab>",
      "ref_bis": "<ref_bis>",
      "a_ab": "<a_ab>",
      "a_bis": "<a_bis>",
      "b_ab": "<b_ab>",
      "b_bis": "<b_bis>",
      "min_paar_min": "<min_paar_min>"
    },
    "name": "wohnmessung_feste_referenz_zwei_rotationsorte"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_abYesBeginn des auswertbaren Messabschnitts A nach Eingewöhnung.
b_abYesBeginn des auswertbaren Messabschnitts B nach Eingewöhnung.
a_bisYesEnde A.
b_bisYesEnde B.
ref_abYesStart der durchgängigen Referenzreihe.
ref_bisYesEnde der Referenzreihe.
min_paar_minYesVerlangte Dauer paariger Messung je Raum in Minuten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. Beyond that, the description does not say what 'coverage' means operationally (whether it returns a boolean, fails, or reports gaps), what happens when min_paar_min is unmet, or any return semantics for a tool with no output schema.

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?

It is a single, front-loaded sentence with the key resources and the check stated immediately. The German/English duplication adds a small amount of redundancy but no real bloat.

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 7-required-parameter, read-only computation with full schema coverage and no output schema, the description covers the core intent. However, it leaves ambiguous how the three time ranges and the minimum paired duration combine into the 'coverage' decision, which is the main thing an agent would need before trusting the result.

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 the schema already defines each parameter, including the A/B measurement sections and the reference series. The description adds a conceptual mapping (ref_* = fixed logger, a/b = rotating rooms, min_paar_min = required paired duration) but no syntax or unit detail beyond the schema, so 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?

The description names a specific check ('simultaneous coverage') over concrete resources: a fixed reference logger plus two rotating room windows. An agent can grasp the operation, though the German phrase 'zeitlich absichern' is vaguer than the English gloss and the tool is not explicitly distinguished from the other wohnmessung siblings.

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 to use this tool versus alternatives such as wohnmessung_logger_uhrdrift_gemeinsamer_stichtag or wohnmessung_nachprobe_raeume_ereignisfenster, nor any prerequisite or exclusion. The user must infer the scenario entirely from the tool name and parameters.

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