Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

asset_prepare

Starts a persistent asset acquisition and preparation job for a plan, then poll job_status to track progress; reuse request_id to reconnect. Preparation alone does not confirm runtime physics success.

Instructions

Start a persistent acquisition/preparation job; poll job_status. Preparation alone does not establish runtime physics success. Reuse request_id to reconnect.

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": {
      "plan_id": "<plan_id>"
    },
    "name": "asset_prepare"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYes
request_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful traits: the job is persistent and asynchronous, results are retrieved via polling, request_id provides reconnection/idempotency, and preparation success does not imply runtime physics success. It does not disclose permissions, expected duration, resources consumed, or whether duplicate submissions without request_id are rejected. Solid but incomplete behavioral coverage for a job-starting mutation.

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, front-loaded with the action, then the polling instruction, then the caveat and idempotency hint. No filler, no restatement of the name, and each sentence carries a distinct piece of information.

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 an async job launcher with no annotations, no output schema and 0% schema coverage, the description covers the lifecycle (start, poll, reconnect) and one important expectation caveat. It still leaves the agent guessing about plan_id provenance, output shape, and cost/duration, which are material for a job-spawning tool.

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%, so the description must compensate for two undocumented parameters. It adds real meaning for request_id (reuse it to reconnect to an existing job), which is exactly the kind of idempotency semantics the schema lacks, but plan_id is never explained at all — no indication of its origin, format, or whether it comes from asset_plan. Roughly half the parameter surface is compensated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The definition gives a clear verb and resource ('Start a persistent acquisition/preparation job') and names the follow-up tool (job_status), so an agent knows this is the async kickoff step. However, 'acquisition/preparation' is left fuzzy, and among siblings like asset_acquire, asset_generate and asset_plan the definition never states which stage this job actually performs or what a 'plan_id' represents. The agent can place the tool in a workflow but not fully distinguish it from the acquisition siblings.

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?

It implicitly defines the usage pattern: call this, then poll job_status, and reuse request_id to reconnect rather than starting a duplicate. What is missing is explicit when-not guidance relative to asset_acquire or asset_generate, and no prerequisite is stated (e.g. that a plan must exist first). Guidance is present but must be inferred from the workflow shape.

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