Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

scene_export

Exports supported scene objects to a USD file at a chosen destination, enabling asset handoff and downstream simulation workflows.

Instructions

Export supported scene objects to a USD file on this server.

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>",
      "destination": "<destination>"
    },
    "name": "scene_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
scene_idYes
destinationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden, yet it only discloses that output lands on the server. It says nothing about whether an existing file at the destination is overwritten, what permissions or authentication are required, what 'supported' excludes, or how failures are reported for a write-to-disk operation.

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 front-loaded sentence with no filler. It is efficient, though the brevity reflects under-specification rather than disciplined editing.

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?

This is a file-producing operation with no annotations, no output schema, and no documented parameters. An agent cannot tell what file it will get back, where exactly it lands, or what it may overwrite — well short of what a tool of this complexity needs.

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% and the description does not compensate. 'destination' is never clarified as a filesystem path, and 'scene_id' is not explained at all, leaving both required parameters ambiguous.

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 clear verb+resource: export scene objects to a USD file. 'Supported scene objects' is mildly vague about scope, and it offers no differentiation from the sibling video_export, so it stops short of a 5.

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?

There is no when-to-use guidance, no prerequisites, and no mention of how this differs from video_export or the scene_plan_* tools. The only contextual hint is 'on this server', which does not help an agent choose between tools.

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