Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

scene_plan_swap_routes

Read-only

Propose swapping two equal-sized, single-class scheduled robot routes, then review bin labels, reachability, and physical results to validate the change.

Instructions

Propose swapping two equal-sized, single-class scheduled robot routes. Review bin labels, reachability 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": {
      "scene_id": "<scene_id>",
      "first_robot": "<first_robot>",
      "second_robot": "<second_robot>"
    },
    "name": "scene_plan_swap_routes"
  }
}

Input Schema

NameRequiredDescriptionDefault
scene_idYes
first_robotYes
second_robotYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations declare readOnlyHint=true, and 'Propose' is consistent with a non-mutating suggestion rather than an applied change. The phrase 'Review bin labels, reachability and physical results' hints at what the proposal evaluates, but it reads more like an instruction to the caller than a disclosure of what the tool returns or checks internally.

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 short, front-loaded sentences with no wasted preamble. The second sentence is vague enough that it earns its place only marginally, but the overall length is appropriate.

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 three-parameter planning tool with no output schema, the definition covers the core action and a precondition but leaves important gaps: the identifiers' format, what a proposal contains, whether it is persisted, and how the swap is subsequently applied. Adequate but not sufficient for confident invocation.

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. It does constrain the robot parameters (equal-sized, single-class) which adds real meaning, but scene_id is entirely unexplained and the description never states that first_robot and second_robot are robot identifiers rather than indices or labels.

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 states a specific verb ('Propose swapping') and resource (two scheduled robot routes) and adds narrowing preconditions: equal-sized and single-class. An agent can distinguish this from scene_plan_interleave or scene_plan_retime by the swap semantics, though no sibling is named explicitly.

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 constraints 'equal-sized, single-class' implicitly define when the tool is applicable, and 'Propose' implies a preview step before committing. However, there is no explicit statement of when to choose this over the other scene_plan_* tools, nor any exclusion or prerequisite guidance.

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