Skip to main content
Glama

getecoback-raumklima

luftreiniger_getrennte_raeume_belegungsueberschneidung

Read-only

Gleichzeitig belegte Zeit in getrennten Zimmern für einen eigenen Luftreiniger-Standortplan bestimmen — Identify simultaneous separate-room demand before sharing one portable purifier.

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": {
      "a_ab_min": "<a_ab_min>",
      "a_bis_min": "<a_bis_min>",
      "b_ab_min": "<b_ab_min>",
      "b_bis_min": "<b_bis_min>",
      "getrennte_zimmer": "<getrennte_zimmer>"
    },
    "name": "luftreiniger_getrennte_raeume_belegungsueberschneidung"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_ab_minYesBeginn des Nutzungsfensters in Raum A, Minuten ab Tagesbeginn.
b_ab_minYesBeginn des Nutzungsfensters in Raum B.
a_bis_minYesEnde des Nutzungsfensters in Raum A am selben Tag.
b_bis_minYesEnde des Nutzungsfensters in Raum B am selben Tag.
getrennte_zimmerYesZwei getrennte Zimmer, die bei paralleler Belegung getrennt betrachtet werden sollen?

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 safety profile is covered. The description adds that this is a planning computation, but it never states what the result looks like (overlap minutes, a boolean, a per-room breakdown), which matters since there is 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?

Two compact clauses, German then English, with the purpose front-loaded and no filler. The bilingual duplication is the only mild redundancy.

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 five-required-parameter computation with no output schema, the description should say what is returned and how the overlap is expressed. It establishes the intent but leaves the result shape and edge-case behavior 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 five parameters (four minute-offset window bounds plus the getrennte_zimmer flag) are already documented in the schema. The description adds no additional semantics such as whether windows may cross midnight or how equal boundaries are treated.

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 computation — simultaneous occupied time across separate rooms — and frames it as input to a purifier placement plan. It is clearly distinguishable from sibling checks like filter or airflow tools, though it does not name any sibling explicitly.

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?

'Before sharing one portable purifier' gives a genuine usage trigger, so the agent knows the decision context. However, there is no explicit when-not guidance and no named alternative for the case where rooms are not shared or occupancy does not overlap.

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