Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

robot_plan_pick_cycle

Read-only

Plan robot pick-and-place cycles by proposing phases for a 4 cm cube, then validate paths and physical results before simulation.

Instructions

Propose experimental robot-specific phases for an approximately 4 cm cube; use $slot and $item to expand with scene_plan_stream. Validate all paths and physical results.

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": {
      "model_directory": "<model_directory>",
      "drop_position": "<drop_position>"
    },
    "name": "robot_plan_pick_cycle"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemNo$item
drop_positionYes
workspace_maxNo
workspace_minNo
model_directoryYes
return_positionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so 'propose' is consistent and the safety profile is known. The description adds that paths and physical results are validated, which is useful behavioral context, but it says nothing about whether proposals are persisted, how expensive the call is, or what happens with the required model_directory.

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 compact sentences with no filler, and the scope constraint is stated up front. The phrasing is terse to the point of being cryptic ('expand with scene_plan_stream'), but nothing is wasted.

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 six-parameter planning tool with no output schema and no parameter descriptions, the definition is under-specified: an agent would not know what a 'phase' output looks like, what coordinate convention drop_position uses, or how workspace bounds interact with the 4 cm assumption.

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% across six parameters, so the description carries the full burden — and it only alludes to $item and implicitly to workspace bounds via the '4 cm cube' remark. drop_position, return_position, workspace_min/max, and model_directory are left entirely unexplained beyond their names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb ('Propose') and a resource ('experimental robot-specific phases') plus a concrete scope ('approximately 4 cm cube'), but 'phases' is never defined, so an agent must infer from the tool name that this is a pick-and-place cycle plan. It does not clearly set itself apart from siblings like scene_plan_stream or robot_suggest_configuration beyond mentioning one of them.

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 hints at a workflow by saying to use $slot and $item to expand with scene_plan_stream, which implies this tool produces a template consumed by another. There is no explicit when-to-use / when-not-to-use guidance, no prerequisites (e.g. needing a prepared robot profile or solved IK), and no stated alternatives.

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