Skip to main content
Glama

getecoback-raumklima

pflege_uebergabe_rueckfrage_zu_geraeteteil

Read-only

Bei geteilter Gerätepflege fehlende Rückmeldungen konkret dem bearbeiteten Teil zuweisen — Show which care stages still need a part-specific confirmation.

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": {
      "identitaet_belegt": "<identitaet_belegt>",
      "vorbereitung": "<vorbereitung>",
      "behaelter": "<behaelter>",
      "einsatzteil": "<einsatzteil>",
      "sichtkontrolle": "<sichtkontrolle>"
    },
    "name": "pflege_uebergabe_rueckfrage_zu_geraeteteil"
  }
}

Input Schema

NameRequiredDescriptionDefault
behaelterYesBeleg für den separaten Behälterschritt.
einsatzteilYesBeleg für die vereinbarte Pflege des zugänglichen Einsatzteils.
vorbereitungYesBeleg für den ersten vereinbarten Vorbereitungsschritt.
sichtkontrolleYesBeleg für die abschließende Sichtkontrolle vor dem nächsten Gebrauch.
identitaet_belegtYesSind Gerät und die getrennt dokumentierten Teile für alle Beteiligten dieselben?

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds that the tool reports which stages still lack part-specific confirmation (useful since there is no output schema). However, it never explains how the enum evidence values are interpreted — in particular whether an 'abweichend' (deviating) stage counts as needing confirmation — which is the core behavioral question for this tool.

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?

A single front-loaded clause names the situation, the gap, and the outcome, followed by a short English gloss. The bilingual duplication is slightly redundant but no sentence is wasted.

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-parameter, all-required query tool with no output schema, the definition conveys the input semantics (via the schema) and the general shape of the answer. It falls short on how the evidence enums map to 'still needs confirmation' and on what the response actually contains (list of stages? per-part summary?), leaving meaningful gaps.

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 five required fields is documented in the schema, so the baseline is 3. The description adds only the loose notion of 'dem bearbeiteten Teil zuweisen', without clarifying how the four stage evidences combine or what role identitaet_belegt plays in the result.

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?

States a specific resource and operation: in shared device care, attribute missing feedbacks to the part actually worked on, and show which care stages still need a part-specific confirmation. An agent can tell this is a status/attribution query over care-step evidence rather than a data-entry tool. It does not name any sibling (e.g. pflege_restaufgaben_mit_einem_gesamtstopp vs. this part-level view), so it stays at 4.

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 context is implied by 'Bei geteilter Gerätepflege fehlende Rückmeldungen' — use it when care is split and confirmations are missing. There are no explicit when-not conditions and no routing to alternatives among the many pflege_* siblings, so the agent must infer boundaries.

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