Skip to main content
Glama

getecoback-raumklima

wohnfeuchte_zwei_raeume_gemeinsame_ereignisse

Read-only

Aus synchronen Messpaaren gemeinsame und einzelne Feuchtespitzen zählen — Separate simultaneous humidity exceedances from room-only events.

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": {
      "paare": "<paare>",
      "a_oben": "<a_oben>",
      "b_oben": "<b_oben>",
      "zugleich": "<zugleich>",
      "gleiches_ziel_und_messabstand": "<gleiches_ziel_und_messabstand>"
    },
    "name": "wohnfeuchte_zwei_raeume_gemeinsame_ereignisse"
  }
}

Input Schema

NameRequiredDescriptionDefault
paareYesZahl synchroner Paare aus vergleichbaren Aufzeichnungsabschnitten.
a_obenYesMesspaare mit Überschreitung des eigenen Beobachtungswerts in A.
b_obenYesMesspaare mit Überschreitung in B.
zugleichYesMesspaare mit Überschreitung in beiden Zimmern.
gleiches_ziel_und_messabstandYesGleiches Beobachtungsziel, gleicher Messabstand und passende Zeitstempel?

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 the agent knows this is a side-effect-free closed-world computation. The description adds that inputs must be synchronous paired measurements, but it does not disclose what happens when gleiches_ziel_und_messabstand is false (rejection, error, or degraded result) — the single most consequential behavior for this tool.

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 with a short English gloss — efficient and immediately readable. The bilingual restatement is mildly redundant but costs little and improves comprehension for mixed-language agents.

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?

There is no output schema, so the description should clarify what is returned; 'zählen' implies two counts (joint and single events) but the exact return shape is unstated. Combined with the unexplained boolean precondition, the definition leaves a real gap for a five-required-parameter computational tool.

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 five parameters are already documented, and the baseline is 3. The description's framing (joint vs. room-only exceedances across synchronous pairs) helps the agent interpret a_oben, b_oben and zugleich as a 2x2-style count decomposition, but it adds nothing about the semantics or consequences of the boolean guard parameter.

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 verb (zählen/separate) and a specific resource (gemeinsame und einzelne Feuchtespitzen aus synchronen Messpaaren), so the agent knows this computes joint vs. room-only exceedance counts. It is clear on its own, but it does not distinguish itself explicitly from near-siblings such as raumluft_zwei_sensoren_platztausch_probe or luftreiniger_filteranzeige_ereignisse_trennen.

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 'aus synchronen Messpaaren' plus the required precondition parameter, which signals the data must come from comparable simultaneous recordings. There is no explicit statement of when to prefer this over a sibling event-splitting tool, nor of what to do when the pairing precondition fails.

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