Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

asset_inspect_local

Read-only

Inspect a USD file on the simulation host to check asset structure and contents; this does not verify physics behavior.

Instructions

Inspect a USD file on the simulation host. Physics behavior is not verified.

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

Input Schema

NameRequiredDescriptionDefault
asset_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful disclosure — that physics behavior is not verified — which warns the agent not to trust the inspection as validation evidence. It does not say what the inspection returns or what file access/permissions are required.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, zero filler, and the host scoping is stated before the caveat. Nothing is wasted or buried.

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 one-parameter read-only tool with no output schema, the essentials are present: what it acts on, where, and the key limitation about physics. Missing pieces are behavioral — whether it parses or merely reads metadata, error behavior on missing/invalid USD, and any access requirements — plus no differentiation from asset_inspect.

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% for the single asset_path parameter, so the description must compensate and only partially does: 'on the simulation host' implies the path resolves on that host rather than elsewhere. It adds no format, extension, absolute-vs-relative, or path-resolution detail.

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+resource: inspect a USD file, and adds the scoping constraint 'on the simulation host'. It is distinguishable from siblings like asset_acquire or asset_generate, though it doesn't clarify how it differs from the similarly named asset_inspect, which is the closest ambiguity.

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 at all — no prerequisites, no indication of when to prefer this over asset_inspect or when a remote/other-host inspection applies. The one implied cue is the 'simulation host' scoping, which an agent must infer means local filesystem-only.

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