Skip to main content
Glama

getecoback-climate-weather

pflege_teilrunde_arbeitsmittel_als_gruppe_zurueck

Read-only

Einfach zusammengehörige Arbeitsteile erst nach vollzähligem Rücklauf als Set zusammenlegen — Find which necessary member is missing from a partial return.

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": {
      "satz_zuordnung": "<satz_zuordnung>",
      "griff": "<griff>",
      "einsatzteil": "<einsatzteil>",
      "schutzzubehoer": "<schutzzubehoer>"
    },
    "name": "pflege_teilrunde_arbeitsmittel_als_gruppe_zurueck"
  }
}

Input Schema

NameRequiredDescriptionDefault
griffYesRücklaufstatus des ersten vorgesehenen Teils.
einsatzteilYesRücklaufstatus des zweiten Teils.
satz_zuordnungYesIst die Kombination der Teile für diese Haushaltstätigkeit eindeutig dokumentiert?
schutzzubehoerYesRücklaufstatus eines ausdrücklich vorgesehenen Zubehörteils.

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 the safety profile is covered. The description adds that the operation targets incomplete returns and yields a missing-member finding, which is real behavioral context, but it never says what happens when all parts are accounted for or what the result looks like in that case.

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?

It is a single tight sentence pair with no filler. The structure weakens slightly because the operational rule comes first and the actual function is demoted behind an em dash.

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?

With four required parameters, three enums, and no output schema, the description should explain the shape of the answer it returns, and it only hints at 'which member is missing.' The read-only nature is covered by annotations, but the outcome semantics for a complete versus partial return remain underspecified.

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 parameters carries its own German description, including the distinction of 'nicht_erforderlich' for Schutzzubehoer, so the schema does the heavy lifting. The description adds only the notion of a 'necessary member,' which vaguely maps to the enum statuses but gives no further interpretation of 'nicht_zugeordnet' or of the satz_zuordnung flag.

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 second clause, 'Find which necessary member is missing from a partial return,' is a concrete verb plus outcome, but the leading clause 'Einfach zusammengehörige Arbeitsteile erst nach vollzähligem Rücklauf als Set zusammenlegen' describes a workflow rule rather than the tool's action, and it is unclear whether the tool assembles a set or only diagnoses a gap. Nothing in the text distinguishes it from the many similarly named pflege_* siblings, so an agent must infer the difference.

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?

There is no explicit when-to-use statement, no conditions under which the tool should not be called, and no named alternative. The phrase 'bei partial return' implies a context, but the agent must guess whether this tool is for checking completeness before packing or for reporting a shortage after the fact.

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