Skip to main content
Glama
Sign In
robotarm

robotarm

by walcorg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

bring_tube

Rotates the cultivation reel to position a specified tube (1-12) in front of the robot arms for access. Requires both hands at home and the operating hand empty.

Instructions

Turn the cultivation reel forward until tube (1-12) faces the arms. The arms turn it themselves; both hands must be at home and the operating hand empty.

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": {
      "tube": "<tube>"
    },
    "name": "bring_tube"
  }
}

Input Schema

NameRequiredDescriptionDefault
handNo
tubeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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. It discloses useful context such as the tube range, the required hand posture, and that the arms turn the reel themselves, but it omits what happens if preconditions are unmet, whether the action can fail, and how the robot reports completion.

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 two tight sentences with no wasted wording. The action is front-loaded, followed by the key mechanical and safety constraints.

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 two-parameter physical action with no annotations and no output schema, the description covers the main action and preconditions but leaves the `hand` argument undefined and does not describe failure or completion behavior. It is adequate but has clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 explain both parameters. It clarifies that `tube` is in the range 1-12, but it does not explain the optional `hand` parameter or what string values it accepts beyond implying an operating hand must be empty.

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 physical action: turning the cultivation reel forward until a chosen tube faces the arms. It is clear what the tool does, but it does not explicitly distinguish itself from the sibling rotate_reel tool.

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?

It gives important preconditions for use: both hands must be at home and the operating hand must be empty. However, it does not explain when to choose this tool instead of rotate_reel or other movement tools, nor does it name any conditions where this tool should not be used.

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