Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

scene_plan_synchronize

Read-only

Propose interleaved spawn times from observed pickup delays, then review, apply, regenerate the case, and verify simultaneous cycles and safety in a new run.

Instructions

Propose interleaved spawn times from observed pickup delays in an intact completed stream run. Review and apply the proposal, regenerate the case, and verify simultaneous cycles and safety in a new run; this is not a guarantee.

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>",
      "job_id": "<job_id>",
      "ids": "<ids>"
    },
    "name": "scene_plan_synchronize"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes
job_idYes
scene_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations declare readOnlyHint=true, but the description instructs the agent to 'apply the proposal, regenerate the case', which are write operations with no explanation of how they reconcile with a read-only tool. The only genuine added disclosure is the caveat 'this is not a guarantee', which usefully signals the result is a heuristic proposal rather than a verified solution.

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, front-loaded with the core action, with no filler words. The second sentence is a compressed run-on that chains four distinct steps without punctuation or objects, so density comes at the cost of clarity.

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?

With no output schema, no parameter descriptions, and only two weak annotations, the description needs to be richer than average; the 'not a guarantee' caveat and the 'intact completed run' precondition help. But it leaves undefined the key terms 'proposal' and 'case' and never says what the tool returns or what the ids must reference.

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%, so the description carries the full burden for scene_id, job_id and ids, and it says nothing about any of them. 'Completed stream run' weakly hints that job_id references a prior run, but what 'ids' selects (cycles? tracks? cases?) is never stated.

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 interleaved spawn times from observed pickup delays in an intact completed stream run.' That is far more than a restatement of the name. It does not, however, distinguish this from near-neighbours like scene_plan_interleave or scene_plan_retime, so an agent cannot tell which tool is the right entry point.

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?

The second sentence sketches a workflow ('Review and apply the proposal, regenerate the case, and verify ... in a new run'), which implies the usage context. But it never states when to choose this over scene_plan_interleave or scene_plan_collision_audit, and it never says whether 'apply' happens here or in a separate tool. Usage is implied, not specified.

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