Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

asset_acquire

Starts downloading a selected USD asset and its dependencies, then poll job_status until complete; use result.root local path for scene_apply and check dependency_status first.

Instructions

Start downloading a selected asset and dependencies. Poll job_status until completed; its result.root is the local USD path for scene_apply. Check dependency_status and unresolved_dependencies 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": {
      "asset_url": "<asset_url>"
    },
    "name": "asset_acquire"
  }
}

Input Schema

NameRequiredDescriptionDefault
refreshNo
asset_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does meaningful work: it discloses that the operation is non-blocking (a job must be polled), that it pulls dependencies transitively, and where the usable result surfaces (job_status result.root). It omits permission/auth requirements, whether an existing local asset is overwritten, and what failure looks like — gaps that matter for a download that mutates local state.

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?

Three short sentences, each doing distinct work: what it does, how to retrieve the result, and what to verify first. The core action is front-loaded and there is no filler or restatement of the name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter async downloader with no output schema and no annotations, the description covers the essential lifecycle — initiation, polling, result handoff, and prerequisite checks. The remaining hole is the refresh flag and the overwrite/error semantics, which an agent would need to call this safely on a second run.

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% across two parameters, so the description must compensate and largely does not. 'Selected asset' loosely implies asset_url is an identifier obtained from a prior search/plan step, but the type and accepted form of the URL are unstated, and the refresh boolean is never mentioned — the agent cannot tell whether it forces a re-download or overwrites an existing local copy.

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 — 'start downloading a selected asset and dependencies' — and makes clear it is an asynchronous kickoff rather than a completed download. It does not, however, distinguish itself from other acquire-shaped siblings such as huggingface_acquire_asset or asset_generate, so the agent must infer the boundary from names alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It spells out the surrounding workflow explicitly: poll job_status until completed, take result.root as the local USD path, and pass that to scene_apply. It also names preconditions (check dependency_status and unresolved_dependencies before use). What it lacks is any statement of when this tool is the wrong choice versus a sibling acquirer, or what to do if a dependency check fails.

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