Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

robot_prepare_profile

Prepares experimental controller files for a selected robot USD on the simulation host and validates compatibility and physical behavior before use.

Instructions

Prepare experimental controller files for one acquired USD on the simulation host. Models: kawasaki_rs007l_rg2, franka_panda, ur10_short_suction. Poll job_status; validate compatibility and physical behavior before use.

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": {
      "model": "<model>",
      "asset_path": "<asset_path>"
    },
    "name": "robot_prepare_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYes
asset_pathYes

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?

With no annotations, the description must carry the full behavioral burden. It usefully discloses that the call starts an asynchronous job requiring polling of job_status and that results must be validated for compatibility and physical behavior, but it omits what files are written, where, whether they persist or overwrite, and what 'experimental' implies about stability.

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?

Three short sentences, front-loaded with purpose before the model list and the polling instruction. The telegraphic style ('Poll job_status') is efficient but slightly clipped; nothing 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?

For a two-required-parameter asynchronous preparation tool with no annotations and no output schema, the definition covers the model choices and the async workflow but leaves return values, failure modes, and the meaning of 'compatibility validation' unaddressed.

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 coverage is 0% and there are no enums, so the description meaningfully compensates by enumerating the three supported model values (kawasaki_rs007l_rg2, franka_panda, ur10_short_suction). It only weakly explains asset_path by implying it must reference an already-acquired USD, with no format or path convention given.

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?

States a specific verb and artifact: prepare experimental controller files for one acquired USD on the simulation host. It is clearly distinct from planning/IK siblings, though it does not explicitly distinguish itself from the similarly named asset_prepare.

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?

Adds workflow guidance ('Poll job_status; validate compatibility and physical behavior before use') which tells the agent this is asynchronous and requires follow-up validation. However, it never says when to prefer this over related siblings like asset_prepare or robot_suggest_configuration, nor what preconditions qualify an asset.

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