Skip to main content
Glama

getecoback-raumklima

luftreiniger_geteilter_raum_sitzplatz_ruheprofil

Read-only

Für zwei Raumaufgaben eine gleichzeitig akzeptierte, am Platz tatsächlich gehörte Lüfterstufe finden — Find a tested purifier setting acceptable to both listeners in the shared room.

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_niedrig_ok": "<a_niedrig_ok>",
      "a_hoch_ok": "<a_hoch_ok>",
      "b_niedrig_ok": "<b_niedrig_ok>",
      "b_hoch_ok": "<b_hoch_ok>",
      "pruefung_gleicher_ort": "<pruefung_gleicher_ort>"
    },
    "name": "luftreiniger_geteilter_raum_sitzplatz_ruheprofil"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_hoch_okYesPerson A hat auch die hohe Stufe vor Ort für dieselbe Aufgabe akzeptiert.
b_hoch_okYesPerson B hat die hohe Stufe vor Ort akzeptiert.
a_niedrig_okYesPerson A hat die niedrige Stufe an ihrem Platz für die konkrete Aufgabe akzeptiert.
b_niedrig_okYesPerson B hat die niedrige Stufe vor Ort akzeptiert.
pruefung_gleicher_ortYesBeide Stufen gehören zur selben Aufstellung und wurden an beiden vereinbarten Plätzen geprüft.

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?

The annotations already mark this as read-only and not open-world, and the description adds relevant behavioral context: the setting must be acceptable to both listeners and actually heard at the seat. It does not explain what result is returned, how the five booleans combine into a decision, or what happens when no mutually acceptable setting exists.

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?

The definition is compact and front-loads the core purpose, with a German statement followed by an English gloss. The bilingual repetition is slightly redundant, but the overall wording is efficient and contains no unnecessary explanation.

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-boolean computation tool with no output schema, the description gives the essential scenario but leaves important gaps. It does not specify the expected return value or how conflicting acceptance inputs are resolved, which an agent would need to invoke and interpret the tool confidently.

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 booleans are already well documented in the schema. The description reinforces that two room tasks and two listeners are involved, but it does not add decision logic or clarify how high/low acceptance booleans interact beyond what the schema already provides.

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 specific action and resource: find a tested purifier fan setting that both listeners accept in a shared room. It adds scope through 'für zwei Raumaufgaben' and 'am Platz tatsächlich gehört', which helps distinguish it from generic purifier tools, but it does not explicitly differentiate itself from any sibling tool.

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 'für zwei Raumaufgaben' and the shared-room consensus framing, so an agent can infer this is for two people agreeing on a fan level. However, there is no explicit when-to-use guidance, no when-not-to-use guidance, and no named alternative tool for related but different purifier checks.

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