Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

scene_plan_retime

Read-only

Propose retimed schedules for selected scene objects while preserving their order and first spawn; review and apply the operations before rerunning the simulation.

Instructions

Propose retiming selected scheduled objects, preserving their order and first spawn. Review and apply the operations, then rerun.

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>",
      "spacing_factor": "<spacing_factor>"
    },
    "name": "scene_plan_retime"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes
scene_idYes
spacing_factorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds the meaningful behavioral invariant that order and first spawn are preserved, and that the tool only proposes operations for later review. That is real context beyond the structured fields. It stops short of explaining failure modes or what happens if spacing_factor conflicts with preserved ordering.

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 sentences, front-loaded with the core action, with no filler. The second sentence is slightly cryptic about who applies the operations, which keeps it from a 5.

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 3-parameter planning tool with no output schema and no per-parameter documentation, the description should explain how the proposed operations are returned and what spacing_factor controls. It covers the intent but leaves the agent unable to call the tool confidently.

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% for all three parameters, so the description carries the full burden. It only hints that 'ids' selects objects and says nothing about what spacing_factor means (a multiplier on gaps? a target interval?) or what scene_id scopes. The most decision-relevant parameter is left to guesswork.

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 names a specific verb and resource: 'Propose retiming selected scheduled objects.' The word 'Propose' signals this is a planning step rather than an execution step, which distinguishes it from apply-style tools. It does not name any planning sibling (e.g., scene_plan_interleave, scene_plan_synchronize), so the boundary between this and other planning tools is left implicit.

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?

'Review and apply the operations, then rerun' implies a plan-then-apply workflow, so an agent can infer this is the first step and something else performs the apply. However, it never names the applying tool or states when to choose this over the other scene_plan_* siblings, and no exclusions are given.

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