Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

scene_plan_stream

Read-only

Plan scheduled workpieces and per-class robot cycles without editing the scene; define routes by robot ID, wait limits, cycles, and optional slots, then apply returned operations with a base revision.

Instructions

Propose scheduled workpieces and per-class robot cycles without editing the scene. Each routes[label] uses robot_id, wait={axis,minimum,maximum,max_steps}, cycle=[phases], and optional slots. Use the cycle returned by robot_plan_pick_cycle; apply returned operations with base_revision.

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": {
      "scene_id": "<scene_id>",
      "prefix": "<prefix>",
      "labels": "<labels>",
      "routes": "<routes>",
      "position": "<position>",
      "size": "<size>"
    },
    "name": "scene_plan_stream"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeYes
labelsYes
prefixYes
routesYes
mass_kgNo
positionYes
scene_idYes
first_stepNo
spawn_stepsNo
interval_stepsNo

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?

Annotations already declare readOnlyHint=true and openWorldHint=false; the description adds that this is a non-editing proposal step and that its output is operations to be applied against a base_revision, which conveys the versioning/apply workflow. It does not describe failure modes or validation behavior, keeping it below a 5.

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?

Three tight sentences, front-loaded with the purpose and followed by the parameter shape and the workflow constraint. The middle sentence is dense but every clause maps to a real schema field; no filler.

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 10-parameter, nested-object tool with no output schema, the description covers the routing structure and the apply workflow but omits most scalar parameters (position, size, spawn_steps, interval_steps) and any statement of what the proposal returns beyond 'operations'. Adequate but with visible gaps.

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 coverage is 0% across 10 parameters, so the description carries the burden. It does document the most complex nested parameter well (routes[label] with robot_id, wait={axis,minimum,maximum,max_steps}, cycle=[phases], slots), but leaves prefix, labels, position, size, mass_kg, first_step, spawn_steps, and interval_steps entirely unexplained.

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?

Uses a specific verb ('Propose') with a concrete resource ('scheduled workpieces and per-class robot cycles') and immediately bounds the scope with 'without editing the scene'. It is distinguishable from mutating siblings like scene_apply, though it does not explicitly differentiate from the similarly named scene_plan_stream_case.

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?

Gives real workflow guidance: obtain the cycle from robot_plan_pick_cycle, then apply the returned operations using base_revision. It stops short of stating when to prefer this over scene_plan_interleave or scene_plan_synchronize, but the prerequisite chain is clear.

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