Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

asset_inspect

Read-only

Inspect a USD asset by URL to retrieve indexed metadata, its dependency graph, and a download size estimate before acquiring or composing it.

Instructions

Retrieve indexed metadata, dependency graph and download estimate.

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_url": "<asset_url>"
    },
    "name": "asset_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
asset_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety and network scope are covered. The description adds useful behavior beyond that by naming the kinds of data returned, including a download estimate that hints at remote sizing. It still does not say what happens for unindexed assets, whether the call is cheap, or how large the dependency graph response can be.

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?

One front-loaded sentence with no filler, and the most important content (what you get back) leads. Brevity here edges toward under-specification rather than verbosity.

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 one parameter, no output schema, and annotations covering safety, the definition is minimally callable. Missing pieces that matter for correct invocation are the notion of 'indexed' (does this fail for unknown URLs?) and any differentiation from asset_inspect_local.

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%, so the single asset_url parameter has no documented format anywhere. The description could have specified accepted URL forms or that it must reference an already-indexed asset, but instead compensates for none of that gap.

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 names a specific verb ("Retrieve") and enumerates concrete return contents: indexed metadata, dependency graph, and download estimate. That is far more informative than the name alone. It stops short of a 5 because "indexed" is undefined and nothing separates it from the sibling asset_inspect_local.

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 statement of when to use this versus asset_inspect_local or asset_search, and no prerequisite such as 'the asset must already be indexed'. The agent must infer selection from the name alone.

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