Skip to main content
Glama

getecoback-climate-weather

werkstatt_mehrfachgriff_platzwechselprobe

Read-only

Greifen und Wiederholen desselben Griffs vor und nach einer neuen Werkzeugposition erfassen. — Measure repeat reaches before and after moving a tool.

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": {
      "aufgaben_pro_platz": "<aufgaben_pro_platz>",
      "fehlgriffe_alt": "<fehlgriffe_alt>",
      "fehlgriffe_neu": "<fehlgriffe_neu>",
      "danach_unterbrochen_neu": "<danach_unterbrochen_neu>"
    },
    "name": "werkstatt_mehrfachgriff_platzwechselprobe"
  }
}

Input Schema

NameRequiredDescriptionDefault
fehlgriffe_altYesZusätzliche Such- oder Korrekturgriffe am bisherigen Platz.
fehlgriffe_neuYesZusätzliche Such- oder Korrekturgriffe am neuen Platz.
aufgaben_pro_platzYesPro Position gleich viele einfache Aufgaben mit demselben Werkzeug.
danach_unterbrochen_neuYesAufgaben, die am neuen Platz nach erfolglosem Greifen unterbrochen wurden.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

The readOnlyHint and openWorldHint annotations already establish a safe, closed-world operation. The description adds the measurement context of before/after tool relocation, but it does not explain how the counts are evaluated, what result is produced, or any validation behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short, front-loaded, and contains no filler. The bilingual German/English phrasing is compact and directly states the purpose.

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 four-parameter measurement tool with no output schema, the description gives enough context to know the general scenario. However, it omits what the tool returns or how the repeated-grasp counts are interpreted, leaving a meaningful gap.

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 schema already documents all four numeric parameters in detail. The description does not add parameter-specific meaning beyond indicating the before/after position comparison.

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 identifies a specific measurement scenario: repeated grasps before and after a tool position change. It is clearer than a tautology and gives the core verb/resource, but it does not explicitly differentiate itself from the many sibling workshop probe tools.

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?

Usage is implied by the before/after tool-position context, but there is no explicit when-to-use guidance, prerequisites, or comparison to sibling tools. An agent can infer the scenario but is not routed between alternatives.

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