Skip to main content
Glama
Sign In
robotarm

robotarm

by walcorg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

pick

Grasp an object at a specified station with a chosen hand for hand-over tasks; use move_object instead for standard object relocation.

Instructions

Grasp the object in a station. Use for hand-overs; prefer move_object otherwise.

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>",
      "station": "<station>"
    },
    "name": "pick"
  }
}

Input Schema

NameRequiredDescriptionDefault
handYes
stationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and mostly drops it: nothing about what happens if no object is present, whether the grasp can fail, required arm pose, or whether the action is reversible. Only the hand-over framing hints at behavior.

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?

Two short clauses, front-loaded with the action and followed by routing guidance; nothing is wasted. The brevity edges into under-specification rather than verbosity, which is the right failure mode for this dimension.

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?

For a manipulation primitive with two undocumented parameters, no annotations, and no output schema, the description does not say enough for an agent to invoke it reliably. Missing preconditions, parameter meaning, and failure behavior make it incomplete relative to the tool's physical consequences.

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 neither 'hand' nor 'station' is documented anywhere. The description implies a station is involved but never explains the hand parameter (e.g., which arm/gripper values are valid) or what a station identifier refers to, leaving both parameters ambiguous.

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 concrete verb and resource ('Grasp the object in a station') so the agent knows this is a grasping action at a named station. It doesn't specify which object or what state the arm must be in, but the action is distinguishable from siblings like place or move_object.

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

Usage Guidelines4/5

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

It explicitly names the intended scenario ('hand-overs') and routes the agent elsewhere when that doesn't apply ('prefer move_object otherwise'). That is real when-to-use/when-not guidance, though it lacks prerequisites such as homing or gripper state.

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