Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

robot_suggest_configuration

Read-only

Suggests an experimental starting controller configuration for a generated robot profile and world base pose, then validates reachability, collisions, and behavior in Isaac Sim.

Instructions

Suggest an experimental starting controller configuration for a generated profile and world base pose; validate actual reachability, collisions and behavior in Isaac.

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_directory": "<model_directory>",
      "base_position": "<base_position>",
      "orientation_wxyz": "<orientation_wxyz>"
    },
    "name": "robot_suggest_configuration"
  }
}

Input Schema

NameRequiredDescriptionDefault
base_positionYes
model_directoryYes
orientation_wxyzYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 non-destructive, closed-world nature is known. The description adds that results are an 'experimental starting' point requiring validation in Isaac, which usefully frames the output as non-authoritative. However, it does not state whether an Isaac session must already be running, how expensive the validation step is, or what a failure looks like.

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?

A single compact sentence with the core action front-loaded; little waste. The only weakness is that it bundles two activities (suggest and validate) without separating which one dominates.

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?

There is no output schema, yet the description never says what is returned (a config object, a validation report, metrics?). For a tool whose whole value is a suggested configuration plus validation results, that omission leaves an agent unable to predict or consume the response.

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% for all three required parameters, so the description carries the full explanatory burden. It loosely maps 'generated profile' and 'world base pose' to model_directory and base_position/orientation_wxyz, but never clarifies whether model_directory is a path to a generated profile or a raw model, and adds no format detail (units, frames) beyond the schema.

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 gives a specific verb and resource: 'suggest an experimental starting controller configuration.' It also names the inputs (generated profile, world base pose), which distinguishes it from siblings like robot_solve_ik or robot_prepare_profile. It is slightly muddled by appending a second apparent function ('validate actual reachability, collisions and behavior in Isaac').

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?

Phrasing such as 'experimental starting configuration for a generated profile' implies this belongs after a profile-generation step, but no explicit when-to-use or when-not-to-use guidance is stated. No alternative tool (e.g. robot_solve_ik, robot_plan_pick_cycle) is named as a contrast, so routing must be inferred.

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