Skip to main content
Glama

getecoback-climate-weather

duschhalter_ablage_position_lieblingshand_wechsel

Read-only

Festhalten, in welchen Schritten bei zwei tatsächlich erprobten Griffabläufen ein Handwechsel nötig war — Compare left/right hand changes in observed retrieval routines.

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": {
      "a_entnehmen": "<a_entnehmen>",
      "a_ablegen": "<a_ablegen>",
      "b_entnehmen": "<b_entnehmen>",
      "b_ablegen": "<b_ablegen>",
      "gleiche_person_aufgabe": "<gleiche_person_aufgabe>"
    },
    "name": "duschhalter_ablage_position_lieblingshand_wechsel"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_ablegenYesHandwechsel beim Zurücklegen mit Ablauf A nötig.
b_ablegenYesHandwechsel beim Zurücklegen mit Ablauf B nötig.
a_entnehmenYesHandwechsel beim Entnehmen mit Ablauf A nötig.
b_entnehmenYesHandwechsel beim Entnehmen mit Ablauf B nötig.
gleiche_person_aufgabeYesGleiche Person und gleiche bewusst gewählte Ausgangshand bei beiden Abläufen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/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, so the safety profile is covered. Beyond that the description adds nothing: it does not say what the agent receives back, how the two routine sets are compared, or what happens when gleiche_person_aufgabe is false. The word "Festhalten" even leans toward persistence, which sits uneasily with readOnlyHint, though not enough to call a contradiction.

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?

A single short sentence with no padding, which is appropriate. But the German and English halves diverge in meaning rather than complementing each other, so the bilingual dash construction creates ambiguity rather than clarity.

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?

Five required booleans and no output schema mean the description should at least indicate what result comes back (e.g., a per-step comparison verdict). It does not, and it also omits any precondition tying the two routines together, leaving the agent without enough to interpret the call.

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 coverage is 100%, so all five booleans, including gleiche_person_aufgabe, are already documented in the schema. The description only adds that routines A and B are actually tested observed procedures, which gives slight meaning to the A/B pairing. Baseline 3 applies when the schema does the heavy lifting.

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 names the resource (Handwechsel/side changes at individual steps across two routines) and the German/English gloss makes the domain recognizable. However, the verb is split between "Festhalten" (record) and "Compare", which are two different operations, so an agent cannot be fully sure whether this tool stores observations or evaluates them. Sibling tools like duschhalter_greifen_zuruecklegen_bewegung_getrennt are not distinguished from it.

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?

No when-to-use condition, no exclusion, and no named alternative. The only contextual hint is the phrase "zwei tatsächlich erprobten Griffabläufen", which implies the tool applies to two observed routines, but nothing tells the agent how that differs from adjacent duschhalter tools.

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