Skip to main content
Glama
rebot-mcp

rebot-mcp

Official

place

Put a held object down by lifting, moving above a target pose or x,y,z point, descending, opening the gripper, and retreating. Optionally keeps the object or stays in place.

Instructions

Put the held object down: lift, move above the target, descend, open the gripper, retreat. Target: a saved pose name (its gripper position is the place point) or x, y, z in m (base frame). rpy_deg optionally sets the orientation [roll, pitch, yaw]. release=false keeps the object, retreat=false stays at the target. Fails with IK_UNREACHABLE / WORKSPACE_VIOLATION (also for keep-out boxes) / TRACKING_STALL / PLACE_TIMEOUT. Needs capability 'place'. Blocks until done.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "place"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
zNo
poseNo
releaseNo
retreatNo
rpy_degNo
timeout_sNo
speed_scaleNo
approach_height_mNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden well: it discloses the motion sequence, failure modes, capability requirement, and blocking behavior. It still does not explain what happens to the held object or robot state after a failed place.

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 dense but front-loaded, starting with the action sequence before target and flag details. Every clause adds operational information without padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter tool with no annotations and no output schema, the description is unusually complete: it covers purpose, target forms, key flags, failures, capability, and blocking. The main gap is incomplete documentation of the remaining motion-control parameters.

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 document all parameters. It explains x/y/z units and frame, saved-pose semantics, rpy_deg, release, and retreat, but omits timeout_s, speed_scale, and approach_height_m.

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 action and resource: putting a held object down, with an explicit lift/move/descend/open/retreat sequence. It is clearly a place operation, but it does not explicitly differentiate itself from siblings such as move_to_pose or release.

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 'Put the held object down' and by the target options, plus the release/retreat flags. However, there is no explicit guidance on when to choose this over release or move_to_pose, and no stated exclusions.

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