Skip to main content
Glama

getecoback-climate-weather

ventilator_leihe_raeume_ruheziel_vorrang

Read-only

Einen erprobten leisen Ventilator zwischen zwei zeitgleichen Nutzungen abstimmen — Resolve competing room slots for one trialled fan.

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": "<a_ab>",
      "a_bis": "<a_bis>",
      "b_ab": "<b_ab>",
      "b_bis": "<b_bis>",
      "a_stufe_passt": "<a_stufe_passt>",
      "b_stufe_passt": "<b_stufe_passt>",
      "vorrang": "<vorrang>"
    },
    "name": "ventilator_leihe_raeume_ruheziel_vorrang"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_abYesBedarf ab Minute in Zimmer A.
b_abYesBedarf ab Minute in Zimmer B.
a_bisYesBedarf bis Minute in A.
b_bisYesBedarf bis Minute in B.
vorrangYesAbgesprochener Vorrang beim Überschneiden.
a_stufe_passtYesLautstärke und Luftstrom waren bei derselben erprobten Stufe in A passend?
b_stufe_passtYesLautstärke und Luftstrom waren bei derselben erprobten Stufe in B passend?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior2/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, but the description adds little beyond the name. It never says what the tool actually produces — a priority decision, an adjusted slot pair, a conflict flag — nor how a 'offen' priority or a failing suitability flag is resolved, which matters 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.

Conciseness3/5

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

It is short and front-loaded, but the second half is a near-verbatim English translation of the German sentence, so roughly half the content is duplication rather than added information. No structural waste beyond that.

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?

For a seven-required-parameter adjudication tool with no output schema, the definition should explain the shape of the answer and the conflict-handling rules. It does neither, leaving an agent able to construct the call but unsure what result to expect or how to interpret it.

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%, and each of the seven parameters carries a German description (minute bounds, suitability booleans, priority enum). The description text itself adds no syntax, unit, or interpretation guidance beyond that, so the schema is doing all the work and 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 states a specific verb and resource: reconciling ('abstimmen') two simultaneous usage windows for a single already-trialled quiet fan. That scope — two overlapping room slots, one device — is concrete enough to separate it from the single-room or schedule-confirmation siblings, though no sibling is named explicitly.

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 only an implied trigger (two rooms needing the fan at overlapping times); the text never says when to call this instead of, say, the noise-compromise or shift-schedule variants. Nothing is said about prerequisites, about what to do when 'vorrang' is 'offen', or about the case where both 'stufe_passt' flags are false.

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