Skip to main content
Glama
rebot-mcp

rebot-mcp

Official

gripper

Open, close, or move a reBot arm's end effector to grasp objects on contact or target a specific aperture, returning holding state, gap, torque, and fraction.

Instructions

Gripper: open, close (grasp=true by default: stops on contact and reports holding) or move to fraction (0 closed .. 1 open). Returns {holding, gap_rad, torque_nm, fraction, state}.

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": {
      "command": "<command>"
    },
    "name": "gripper"
  }
}

Input Schema

NameRequiredDescriptionDefault
graspNo
commandYes
fractionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 disclosure burden. It does well on the non-obvious part — the default grasp behavior stops on contact and reports holding — but says nothing about preconditions (enable/take_control), error or blocked states, whether a move is blocking, or safety implications.

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?

A single dense sentence, front-loaded with the resource and commands, then semantics, then return shape. Every clause carries information; the parenthetical nesting makes it slightly harder to parse than a short bulleted form would be.

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 3-parameter, annotation-free tool with no output schema, the description covers both the command semantics and the returned fields {holding, gap_rad, torque_nm, fraction, state}, which is the main completeness win. Missing preconditions and failure behavior keep it short of fully self-sufficient.

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

Parameters4/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, and it largely does: it gives the physical meaning of fraction (0 closed .. 1 open), which the schema only bounds numerically, and explains that grasp defaults to true with contact-stopping behavior. It omits that fraction is only meaningful for command=move and that grasp only applies to close, and its 'true by default' sits slightly awkwardly against the schema's default of null.

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?

States a specific resource (the gripper) and enumerates its three commands (open, close, move) with the meaning of each, so the agent knows exactly what the tool controls. It does not, however, distinguish itself from gripper-related siblings such as place or release, leaving that boundary to inference.

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 command semantics rather than stated: nothing says when to prefer this over place/release, whether a prior enable or take_control is required, or what to do on failure. The one genuinely useful guidance — that close with grasp=true stops on contact — is buried in a parenthetical rather than framed as a usage rule.

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