Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

scene_plan_translate_group

Read-only

Propose moving scene objects by a world-space delta and optionally translate one robot's selected nearby waypoints, then review returned phase indices and rerun as needed.

Instructions

Propose moving objects by a world-space delta and optionally moving one robot's explicitly selected nearby absolute waypoints. Review the returned phase indices and 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>",
      "delta": "<delta>"
    },
    "name": "scene_plan_translate_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes
deltaYes
scene_idYes
move_targetsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so non-mutation is established; the description reinforces this with 'Propose'. It adds real behavioral context beyond the annotations: the delta is world-space, the waypoint handling is restricted to one robot's explicitly selected nearby waypoints, and the response exposes phase indices that may require rerunning. It omits what happens to the proposal afterward (persistence, commit path).

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 tight sentences with the primary operation front-loaded and the review/rerun instruction trailing where it belongs. 'Phase indices' is introduced without explanation, making the second sentence slightly opaque for its brevity.

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, the description at least signals that the return includes phase indices, but it does not explain their meaning, whether the proposal is stored, or how it is later applied. For a four-parameter planning tool with zero schema documentation, this is adequate but leaves notable 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 description coverage is 0%, so the description must carry parameter meaning. It clarifies that 'ids' refers to objects and that 'delta' is a world-space translation, which is genuinely useful, but scene_id is never addressed and the move_targets phrasing ('one robot's explicitly selected nearby absolute waypoints') is dense enough that the expected object shape remains unclear.

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 action (propose a translation) and resource (a group of objects identified by ids), plus a secondary capability (moving one robot's selected nearby absolute waypoints). 'Propose' vs. implied apply/commit distinguishes it from a mutation path, though no sibling such as scene_apply 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 closing sentence gives a workflow cue — inspect the returned phase indices and rerun — which implies this is a propose-then-review cycle. However, it never states when to choose this tool over related planning tools (retime, swap_routes, interleave) or how a plan is later committed, leaving selection largely to inference.

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