Skip to main content
Glama

getecoback-climate-weather

luftreiniger_zwei_raeume_tauschen_nur_beide_teilzeiten

Read-only

Ein vorhandenes Gerät nur dann nacheinander teilen, wenn beide abgesprochenen Raumfenster vollständig bleiben — Test a purifier loan with explicit preferred partial-booking alternatives.

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_besteht_min": "<a_besteht_min>",
      "a_optional_min": "<a_optional_min>",
      "b_besteht_min": "<b_besteht_min>",
      "transfer_min": "<transfer_min>",
      "gesamtrahmen_min": "<gesamtrahmen_min>"
    },
    "name": "luftreiniger_zwei_raeume_tauschen_nur_beide_teilzeiten"
  }
}

Input Schema

NameRequiredDescriptionDefault
transfer_minYesBeobachtete Gesamtzeit für die vorgesehenen Transfers.
a_besteht_minYesFür A unbedingt benötigte vorhandene Dauer.
b_besteht_minYesFür B unbedingt benötigte Dauer.
a_optional_minYesWeitere, ausdrücklich freigegebene optionale Dauer in Raum A.
gesamtrahmen_minYesFür beide Räume nach Absprache verfügbares Gesamtfenster.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior3/5

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

The readOnlyHint=true and openWorldHint=false annotations already establish that this is a safe, closed-world read operation. The description adds a meaningful behavioral constraint about only sharing sequentially when both room windows remain complete, which goes beyond the annotations. It still does not explain the result produced or what happens when the condition fails.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is short, but it mixes German and English in a way that feels disjointed rather than structured. The core conditional is front-loaded, yet the English sentence reads like an appended note and does not reinforce the tool's purpose. It is concise but less clear than a clean single-language description would be.

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?

This is a five-parameter required-input tool with no output schema, so the description should clarify what the tool returns or decides. It never states whether the output is a boolean feasibility result, a schedule, or a recommended allocation. The schema documents the parameters, but the overall behavior remains under-specified.

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 five required numeric parameters documented in German. The description adds no parameter-level meaning beyond the schema, such as how transfer_min interacts with gesamtrahmen_min or what values indicate infeasibility. With full schema coverage, a baseline score of 3 is appropriate.

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 identifies a conditional operation: sharing an existing device sequentially only when both agreed room windows remain complete. However, it does not clearly state whether the tool checks feasibility, computes a schedule, or returns a decision. The English fragment adds ambiguity rather than sharpening the purpose, and no sibling alternative is named.

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?

The only usage condition is the embedded constraint that both agreed room windows must remain fully intact. There is no explicit guidance on when to choose this tool over the many sibling air-purifier tools, nor are alternatives or exclusions identified. The mention of 'preferred partial-booking alternatives' is too vague to function as routing guidance.

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