Skip to main content
Glama

getecoback-climate-weather

pflegegruppe_ein_teil_bearbeitet_rest_nachhalten

Read-only

Eine bestätigte Gruppenpflege nach einem betroffenen Einzelteil erneut abgrenzen — Identify which finished groups need a repeat check after one piece was involved.

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": {
      "trennung_belegt": "<trennung_belegt>",
      "teil_a": "<teil_a>",
      "teil_b": "<teil_b>",
      "teil_c": "<teil_c>",
      "folge_bekannt": "<folge_bekannt>"
    },
    "name": "pflegegruppe_ein_teil_bearbeitet_rest_nachhalten"
  }
}

Input Schema

NameRequiredDescriptionDefault
teil_aYesBeobachtung zur fertig abgelegten Gruppe A.
teil_bYesBeobachtung zur fertig abgelegten Gruppe B.
teil_cYesBeobachtung zur fertig abgelegten Gruppe C.
folge_bekanntYesIst die gegebenenfalls nötige Reaktion für betroffene Teile dokumentiert?
trennung_belegtYesSind Gruppen und Ereignis vor Ort eindeutig erfasst?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with a pure evaluation tool. Beyond that it adds only the scenario; it says nothing about what the determination produces, how the boolean gates ('trennung_belegt', 'folge_bekannt') influence the result, or that nothing is persisted.

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 sentence, no padding. The same statement is repeated in German and English, which is slightly redundant but keeps the definition short and readable.

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 five-required-parameter classification tool with no output schema, so the description must explain the shape of the verdict ('which groups need a repeat check'). It does not: it never clarifies what the answer looks like or how conflicting observations (e.g. 'offen' vs 'getrennt') are resolved.

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% with enums documented for teil_a/b/c, so the schema carries all parameter meaning. The description mentions no individual parameters, so 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 gives a verb ('erneut abgrenzen' / 'identify') and a resource ('bestätigte Gruppenpflege' / 'finished groups needing a repeat check'), so the general intent is graspable. However the phrasing is abstract domain jargon ('abgrenzen') and it never distinguishes this tool from similarly named siblings such as pflegegruppe_abtropfplatz or pflege_behaelter_rest_neben_haushaltsbedarf.

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?

The clause 'nach einem betroffenen Einzelteil' hints at a trigger situation, but there is no explicit when-to-use, no when-not-to-use, and no named alternative. The agent must infer the operational context from a single prepositional phrase.

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