Skip to main content
Glama

getecoback-climate-weather

ventilator_teilraum_hin_und_rueckgabe

Read-only

Eine kurze Ausleihe mit zwei abgesprochenen Transfers zwischen belegten Räumen vergleichen — Check whether a fan loan can fit both transfers before the lender’s next use.

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": {
      "erster_raum_frei_min": "<erster_raum_frei_min>",
      "hin_transfer_min": "<hin_transfer_min>",
      "gewaehlt_nutzung_min": "<gewaehlt_nutzung_min>",
      "rueck_transfer_min": "<rueck_transfer_min>",
      "erster_raum_benoetigt_min": "<erster_raum_benoetigt_min>"
    },
    "name": "ventilator_teilraum_hin_und_rueckgabe"
  }
}

Input Schema

NameRequiredDescriptionDefault
hin_transfer_minYesBeobachteter Aufwand bis zur erlaubten Nutzung im zweiten Raum.
rueck_transfer_minYesBeobachteter Rückgabeaufwand bis zum zugelassenen Platz.
erster_raum_frei_minYesErster Raum gibt das Gerät ab dieser Minute frei.
gewaehlt_nutzung_minYesGeplante Nutzungsdauer im zweiten Raum.
erster_raum_benoetigt_minYesErster Raum benötigt das Gerät wieder ab dieser Minute.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is clear. The description adds that this is a comparison/check of whether a loan fits, but it does not describe the result shape or any assumptions about occupied rooms and transfer timing.

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 presents a German sentence followed by an English gloss that largely repeats the same idea. The operative condition is understandable, yet the bilingual duplication and initial 'vergleichen' phrasing make it less front-loaded than it could be.

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 read-only five-parameter feasibility check with no output schema, the description conveys the central question but does not explain the return value or edge-case semantics. It is minimally adequate, but an agent would still need to infer how the result should be interpreted.

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 numeric parameters are already documented in the input schema. The description reinforces the overall scenario of two transfers between occupied rooms, but it adds no parameter-specific meaning beyond the schema.

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 check: whether a short fan loan with two agreed transfers between occupied rooms can fit before the lender’s next use. It is clear enough to identify the operation as a feasibility comparison, though it does not distinguish this tool from similar ventilator-loan siblings.

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?

The phrase 'before the lender’s next use' implies the usage context, but the description does not explicitly say when to choose this tool over related ventilator loan or scheduling tools. Alternative selection is left to inference from the sibling names or schemas.

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