Skip to main content
Glama
Sign In
robotarm

robotarm

by walcorg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

home

Moves a robot hand to its reference pose without releasing held objects, keeping the current grip intact.

Instructions

Return a hand to its home pose without releasing what it holds.

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

Input Schema

NameRequiredDescriptionDefault
handYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 burden, and it does disclose one genuinely useful behavioral trait: the grasp is preserved during the motion. It says nothing about motion speed/path, collision behavior, whether the hand must be idle or enabled, or what happens if the hand is already home — gaps that matter for a motion command.

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?

A single sentence with no filler, and the most decision-relevant detail (the grasp is kept) is placed immediately after the action. Nothing could be removed without losing content.

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 one-parameter action with no annotations and no output schema, the description covers the action and one behavioral guarantee but leaves the parameter's accepted values and the return/feedback unknown. An agent can form the intent but may not be able to fill in 'hand' correctly on the first try.

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

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required parameter, 'hand', typed only as a free string with 0% schema description coverage and no enum. The description adds no meaning about whether this is a hand name, index, or ID, nor how to obtain valid values from siblings like get_scene or get_workcell, so the parameter is effectively undocumented.

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 gives a specific verb and target ('Return a hand to its home pose') rather than restating the name, so the agent knows this is a homing move. It does not explicitly separate itself from the sibling 'reset', which could plausibly also move things to a rest state.

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 only implied: the clause 'without releasing what it holds' hints that this is the move to use while grasping an object, which is a useful situational cue. There is no explicit when-not guidance and no named alternative (e.g. 'use reset to home the whole workcell'), so the agent must infer selection against 'reset', 'stop', and 'move_object'.

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