Skip to main content
Glama
Sign In
robotarm

robotarm

by walcorg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

rotate_reel

Advance a robot arm's reel forward by a specified number of positions with one hand for exact ratchet adjustments; use when precise step counts are needed.

Instructions

Advance the reel a number of positions with one hand. Forward only (ratchet). Prefer bring_tube unless you need an exact number of steps.

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": {
      "hand": "<hand>",
      "steps": "<steps>"
    },
    "name": "rotate_reel"
  }
}

Input Schema

NameRequiredDescriptionDefault
handYes
stepsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the most important trait: the motion is one-directional (ratchet), so it cannot be undone by negative steps. It omits other relevant behavior — what happens if steps exceed remaining reel travel (error vs. clamp), whether the call blocks until motion completes, and speed/timing.

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?

Two short sentences, no filler, with the operational constraint (forward only) front-loaded before the sibling recommendation. Every clause earns its place.

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 simple two-parameter motion primitive the description covers identity, direction constraint, and tool selection, but with no annotations and no output schema it should also say what a call returns or how out-of-range steps fail. Adequate, not complete.

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 0%, so the description must compensate; it partially does by implying steps are reel positions and hand selects which arm acts. It still gives no valid range for steps, no allowed values for hand, and no units, leaving both parameters under-specified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Advance the reel") plus the scope that matters: discrete positions, one hand, forward-only ratchet. It also names the sibling bring_tube, so an agent can distinguish it from the coarser tube-moving tool without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Prefer bring_tube unless you need an exact number of steps" gives an explicit alternative and the exact condition that selects this tool over it. That is the when-to-use vs. when-to-use-something-else decision an agent needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools