Skip to main content
Glama

getecoback-climate-weather

pflege_entnahmeteil_nachlauf_fremde_benutzung

Read-only

Nach einer dokumentierten Zwischenentnahme feststellen, welche spätere Benutzung die ursprüngliche Pflegeprüfung berührt — Check if interim use invalidates one part’s prior handover check.

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": {
      "ereignisse_belegt": "<ereignisse_belegt>",
      "pflege_ende": "<pflege_ende>",
      "entnahme_min": "<entnahme_min>",
      "entnahme_nachbearbeitung": "<entnahme_nachbearbeitung>",
      "rueckgabe_ohne_nutzung": "<rueckgabe_ohne_nutzung>"
    },
    "name": "pflege_entnahmeteil_nachlauf_fremde_benutzung"
  }
}

Input Schema

NameRequiredDescriptionDefault
pflege_endeYesTagesminute der bestätigten Pflege an diesem Teil.
entnahme_minYesTagesminute der folgenden Zwischenentnahme.
ereignisse_belegtYesSind die Ereignisse am selben zugänglichen Teil lückenlos in ihrer Zeitfolge belegt?
rueckgabe_ohne_nutzungYesWurde das Teil ohne Benutzung und unter dokumentiert gleichen zulässigen Bedingungen zurückgegeben?
entnahme_nachbearbeitungYesIst nach dieser Entnahme laut passender Anleitung erneut ein Bearbeitungsschritt erforderlich?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 by structured data. The description adds the meaningful precondition that the removal must be documented and that the original care check is the thing under question, but it never says what the tool returns (a verdict? a classification?) despite there being 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?

The description is short and front-loads the precondition, which is good. But it is the same sentence stated twice in German and English with no extra information in either version, so half the text is pure translation overhead rather than added value.

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?

This is a domain decision tool with five required inputs and no output schema, so the description carries the burden of explaining what determination is produced and how the documented-event constraint affects the result. It says nothing about the outcome, the decision rule, or the failure mode when ereignisse_belegt is false, leaving the agent unable to predict the return value.

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 parameters (pflege_ende, entnahme_min, ereignisse_belegt, entnahme_nachbearbeitung, rueckgabe_ohne_nutzung) are documented in the schema itself. The description only gestures at the concept of documented events and adds no format, ordering, or interaction semantics beyond the schema, so the 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 verb 'feststellen' plus the object 'welche spätere Benutzung die ursprüngliche Pflegeprüfung berührt' identifies the tool as a post-hoc validity assessment, and the English gloss 'check if interim use invalidates one part's prior handover check' sharpens it. However, 'berührt' (touches/affects) is left undefined, and nothing in the text distinguishes this check from the many sibling pflege_* follow-up checks.

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 opening clause 'Nach einer dokumentierten Zwischenentnahme' establishes an implicit trigger condition, so an agent can infer the situation in which to call it. There is no explicit when-not guidance, no mention of an alternative tool, and no statement about what to do when the interim removal is not documented.

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