Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

scene_plan_collision_audit

Read-only

Propose discrete overlap monitoring and model-specific mechanical exceptions for robot paths, then apply collision policies, regenerate the case, and rerun verification.

Instructions

Propose discrete overlap monitoring and model-specific mechanical exceptions for supported robot paths or matching generated profiles. Include every robot in the stream case, review exclusions, apply operations, regenerate the case, add collision_policy and run verification. This does not certify swept-path or real-robot safety.

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>",
      "robot_ids": "<robot_ids>"
    },
    "name": "scene_plan_collision_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
scene_idYes
robot_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior1/5

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

Annotations declare readOnlyHint=true, yet the description instructs the agent to 'apply operations', 'regenerate the case' and 'add collision_policy', all of which are state-changing. A reader cannot tell whether the tool proposes changes or performs them. The only genuinely useful disclosure is the closing scope limit, that it does not certify swept-path or real-robot safety.

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?

It is short and the safety disclaimer is well placed at the end, but the middle sentence is a comma-spliced run-on of six imperatives without ordering or grouping. 'Include every robot in the stream case' and 'regenerate the case' overlap in intent without being reconciled.

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 two-parameter tool with no output schema and only a read-only annotation, the description leaves out return values, what 'operations' or 'exclusions' refer to, and what verification produces. Vague workflow language plus a read-only annotation is not enough for an agent to call this correctly.

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 the parameter meaning. It does add one real constraint: robot_ids should include every robot in the stream case. Beyond that, scene_id is never explained and neither parameter's format or relationship to 'the case' is clarified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gestures at the resource (robot paths / generated profiles, collision_policy) but the verb phrase is opaque jargon: 'Propose discrete overlap monitoring and model-specific mechanical exceptions'. It never says plainly that this audits collision policy for a scene plan, and nothing distinguishes it from scene_validate or scene_compile_recipe.

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 is an imperative workflow ('include every robot', 'review exclusions', 'apply operations', 'regenerate the case'), not when-to-use guidance. No condition selects this tool over scene_validate or scene_plan_stream_case, and no prerequisites or preconditions are stated.

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