Skip to main content
Glama

getecoback-climate-weather

pflege_ausruestung_geordneter_handwechsel

Read-only

Mit beobachteten Handgriffen prüfen, ob die nötigen Teile ohne ungeplante gemeinsame Ablage erreichbar bleiben — Find handover steps that need an independent temporary place.

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": {
      "handgriffe_geprueft": "<handgriffe_geprueft>",
      "greifmittel": "<greifmittel>",
      "schon_sicher_abgestellt": "<schon_sicher_abgestellt>",
      "zwischenplaetze": "<zwischenplaetze>",
      "griff_brauch_frei": "<griff_brauch_frei>"
    },
    "name": "pflege_ausruestung_geordneter_handwechsel"
  }
}

Input Schema

NameRequiredDescriptionDefault
greifmittelYesTeile, die beim ersten geplanten Griff beide Hände oder denselben Ablagepunkt belegen.
zwischenplaetzeYesWeitere passende freie Zwischenplätze vor dem nächsten Griff.
griff_brauch_freiYesBenötigt der nächste Griff vorher alle bisher noch gehaltenen Teile weggelegt?
handgriffe_geprueftYesStammen alle Zahlen aus derselben beobachteten Folge mit passenden Stellplätzen?
schon_sicher_abgestelltYesDavon vor dem nächsten Griff getrennt und geeignet abgelegt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with a non-mutating check. It adds the domain constraint about avoiding unplanned shared placement, but it does not describe the return value, how the check is computed, or what output the agent should expect.

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?

The definition is a single front-loaded sentence and is not padded. However, the German and English halves partly restate the same idea, and the abstract terms reduce crispness slightly.

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-required-parameter, read-only analysis tool with no output schema, the description explains the purpose but not what result is returned or how the agent should interpret the outcome. It is adequate but leaves meaningful gaps about the tool's output and evaluation logic.

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 the input schema already explains all five parameters. The description adds no additional meaning about how the counts and booleans combine, so the baseline of 3 is appropriate.

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?

The description states a specific check with an observable method: use observed hand movements to verify whether needed parts remain reachable without unplanned shared placement, and find handover steps requiring an independent temporary place. The verb and subject are clear, but the definition does not distinguish this tool from the many sibling pflege 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 gives an implied context by saying the check uses observed hand movements, but it never states when to use this tool instead of alternatives, when not to use it, or which sibling tool handles adjacent cases. The agent receives no explicit routing guidance.

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