Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

scene_plan_rope

Read-only

Plan a physical rope as colliding capsule links joined by passive spherical joints from a world-space polyline, with slack and optional end attachments, returning operations for review.

Instructions

Propose real colliding capsule links connected by passive spherical joints. points are a metric world polyline, including deliberate slack. Optional start/end attachments each use body and local_position_m. Apply returned ordinary operations after review. This is not a distance-only or animated rope; routing over a free pulley and actual tension transfer need physical trials and broken-end controls.

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>",
      "prefix": "<prefix>",
      "points": "<points>"
    },
    "name": "scene_plan_rope"
  }
}

Input Schema

NameRequiredDescriptionDefault
pointsYes
prefixYes
physicsNo
radius_mNo
scene_idYes
attachmentsNo
max_segment_mNo
self_collisionNo
linear_density_kg_mNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds the important nuance that the tool returns operations to be applied after review rather than mutating the scene itself. It also discloses that points intentionally include 'deliberate slack,' which is non-obvious behavior for a physical rope. It does not describe what the returned operations look like or how many, and gives no indication of cost or failure modes when geometry is invalid.

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?

The purpose is front-loaded in the first sentence, and each subsequent sentence adds a distinct piece of information: coordinate semantics, attachment structure, next step, and exclusions. The language is dense and domain-specific ('capsule links', 'passive spherical joints', 'tension transfer') but not padded. No sentence is redundant.

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 does say it returns 'ordinary operations' to apply after review, which partially covers the return side. However, for a nine-parameter planning tool with two opaque free-form objects (physics, attachments), a zero-coverage schema, and no annotations about inputs, the description leaves too many knobs undocumented for an agent to call it 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% across nine parameters, so the description must carry the load and it only partially does. It explains points (metric world polyline with deliberate slack) and the attachments object's 'body' and 'local_position_m' keys, which the schema does not, but leaves prefix, scene_id, radius_m, max_segment_m, self_collision, linear_density_kg_m, and the entirely opaque 'physics' object wholly unexplained.

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 real colliding capsule links connected by passive spherical joints,' which tells an agent this builds a simulated rope from capsule primitives rather than drawing a line. The exclusions ('not a distance-only or animated rope') sharpen the boundary further. It stops short of naming which sibling tool consumes the result, leaving the workflow step only implied by 'apply returned ordinary operations.'

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states a when-not case: free-pulley routing and actual tension transfer 'need physical trials and broken-end controls,' which is exactly the kind of exclusion an agent needs. It also gives the follow-up step ('Apply returned ordinary operations after review'), making the review-then-apply workflow clear. It does not name any alternative planning sibling to route to when this tool is unsuitable.

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