Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

scene_plan_interleave

Read-only

Propose a class-aware round-robin spawn schedule that preserves item order within each class, then validate robot timing, regenerate the scene, and rerun physics.

Instructions

Propose a class-aware round-robin spawn schedule while preserving each class's item order. Review robot timing and other objects, apply operations, regenerate the case, and rerun physics.

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>",
      "ids": "<ids>",
      "class_order": "<class_order>",
      "interval_steps": "<interval_steps>"
    },
    "name": "scene_plan_interleave"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes
scene_idYes
first_stepNo
class_orderYes
interval_stepsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior1/5

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

The annotations declare readOnlyHint=true and openWorldHint=false, yet the description instructs the agent to 'apply operations, regenerate the case, and rerun physics' — wording that reads as mutation. Nothing clarifies that these are follow-up actions outside this call, nor does the description disclose what the returned schedule contains or whether it is persisted. This actively conflicts with the declared safety profile.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, but they mix two different purposes: the first states the tool's action, the second drifts into downstream workflow narration that is not about this call. The useful content is front-loaded, yet the second sentence introduces confusion rather than value.

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 read-only planning tool with no output schema and five undocumented parameters, the description should define what a 'class' is, what the schedule output looks like, and how interval_steps/first_step shape it. It instead spends its second half on post-processing steps, leaving the parameter and return semantics under-covered.

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 five parameters, so the description carries the full burden. It only gestures at class_order ('class-aware', 'each class's item order'); ids, scene_id, interval_steps, and first_step are never explained, and the round-robin cadence/timing semantics of interval_steps and first_step remain undefined.

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 first sentence gives a specific verb and resource: 'Propose a class-aware round-robin spawn schedule while preserving each class's item order.' An agent can tell this is a planning/scheduling operation rather than an apply or audit operation. It does not name any sibling (e.g., scene_plan_stream or scene_plan_retime) to distinguish itself from closely related planning tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The second sentence sketches a surrounding workflow ('Review robot timing and other objects... regenerate the case, and rerun physics') but never states when to choose this tool over the many sibling scene_plan_* planners. There are no prerequisites, exclusions, or selection criteria, leaving the agent to infer usage from the name alone.

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