Skip to main content
Glama

getecoback-raumklima

geraet_service_ersatzfunktion_voruebergehend_decken

Read-only

Bei einem geliehenen oder vorhandenen Ersatzgerät einzelne bestätigte Kernfunktionen von offenen Aufgaben trennen — Check temporary task coverage while the original appliance is at service.

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": {
      "pflichtaufgaben": "<pflichtaufgaben>",
      "ersatz_belegt": "<ersatz_belegt>",
      "vorhandenes_verfahren": "<vorhandenes_verfahren>",
      "mehrarbeit_min": "<mehrarbeit_min>"
    },
    "name": "geraet_service_ersatzfunktion_voruebergehend_decken"
  }
}

Input Schema

NameRequiredDescriptionDefault
ersatz_belegtYesDavon mit dem Ersatzgerät vergleichbar beobachtet.
mehrarbeit_minYesBereits geschätzte Mehrarbeit für alle erfassten Übergangslösungen pro Woche.
pflichtaufgabenYesEinzeln erfasste Pflichtaufgaben während der Abwesenheit des Geräts.
vorhandenes_verfahrenYesZusätzliche Pflichtaufgaben, die ein vorhandenes Verfahren vollständig übernimmt.

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds scenario context (temporary coverage via a borrowed/existing substitute device) but does not disclose the calculation logic, whether a threshold or verdict is produced, or any interpretation of the resulting figures. Modest value over annotations.

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?

Two short clauses with no padding, but the bilingual restatement is not additive — the second half repeats rather than sharpening the first. Front-loading exists but the lead clause is the vague one, so little is gained.

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?

Four required numeric parameters and no output schema, so the description must explain what result is produced and how it should be read — it does neither. An agent knows the general scenario but not what it will get back or how mehrarbeit_min factors into the outcome.

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 four numeric parameters carries its own German description with bounds, so the schema does the heavy lifting. The description's phrase about separating confirmed core functions loosely connects to ersatz_belegt versus pflichtaufgaben, but it never explicitly maps inputs to meaning beyond that. Baseline 3 applies.

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 names the scenario (a loaned or existing substitute device while the original is at service) and gestures at the operation ("einzelne bestätigte Kernfunktionen von offenen Aufgaben trennen" / "Check temporary task coverage"). But the two halves point in different directions — one says 'separate functions from tasks', the other says 'check coverage' — and neither states concretely what the tool computes or returns. It is not differentiated from the many sibling geraet_service_* tools.

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?

It implies the situation in which the tool applies (original appliance at service with a replacement device), but gives no explicit when-to-use versus alternatives, no prerequisites, and no exclusions. With ~30 sibling tools in this namespace, routing guidance is entirely absent.

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