Skip to main content
Glama

getecoback-raumklima

geraetepool_ausfall_uebernahme_exklusiv

Read-only

Nach einem Geräteausfall prüfen, wie viele dokumentierte Aufgaben das verbleibende Gerät tatsächlich übernehmen kann — Recover only interchangeable work from a measured failed-device backlog.

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_nur_ausgefallen": "<a_nur_ausgefallen>",
      "a_verlagerbar": "<a_verlagerbar>",
      "b_eigenbelegung_min": "<b_eigenbelegung_min>",
      "b_verfuegbar_min": "<b_verfuegbar_min>",
      "dauer_uebernahme_min": "<dauer_uebernahme_min>"
    },
    "name": "geraetepool_ausfall_uebernahme_exklusiv"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_verlagerbarYesNoch offene Aufgaben, die laut bestätigtem Ablauf beide Geräte erledigen können.
b_verfuegbar_minYesTatsächlich nutzbare Gesamtzeit des verbleibenden Geräts.
a_nur_ausgefallenYesNoch offene Aufgaben, die nur am ausgefallenen Gerät erledigt werden können.
b_eigenbelegung_minYesBelegte Zeit des verbleibenden Geräts für seine eigenen Aufgaben.
dauer_uebernahme_minYesVollständig gemessene Dauer je übernommener Aufgabe am verbleibenden Gerät.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/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 real semantic content beyond that: only interchangeable work counts, tasks exclusive to the failed device are not recovered, and the backlog is 'measured' rather than estimated. It does not describe the return shape (count vs. ratio), which is the main remaining gap for an output-schema-less tool.

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 core constraint is front-loaded, which is good. But the definition is essentially the same statement twice (German then English), and the English half is a compressed restatement rather than new information; the duplication costs space without adding much beyond 'interchangeable' and 'measured'.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-required-numeric-parameter pure computation, the definition supplies the trigger context, the scope limit (interchangeable work only), and the nature of the result (a count of tasks that can be taken over). Combined with a fully described schema and read-only annotations, an agent has enough to invoke it correctly; the exact return format is the only unspecified detail.

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 every parameter is already documented with range and meaning in the schema. The description only restates the overall concept and adds no per-parameter guidance such as how the remaining device's free time is derived. Baseline 3 applies since the schema carries the weight.

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 German sentence names a concrete computation: after a device failure, determine how many documented tasks the surviving device can actually absorb. The English coda sharpens the scope to 'interchangeable work' from a 'failed-device backlog'. It is clear what the tool computes, though the 'exklusiv' qualifier in the name is never explained relative to a non-exclusive variant.

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 trigger condition ('Nach einem Geräteausfall') is stated, which implies when to reach for it. However, no alternative tool is named and no exclusion is given — for example, whether this is the right choice when no task is interchangeable, or which sibling handles the non-exclusive/modus comparison. Usage is inferable but not routed.

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