Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

asset_generate

Starts a durable Sand3D runtime job from a fixed template and structured dimensions, returning an AssetRef for asset planning or preparation; generation alone does not grant a physical pass.

Instructions

Start a durable job for an explicitly configured independent Sand3D runtime and a shipped fixed template (guide_plate_v1 or open_receiver_v1). Accepts structured dimensions only, never external programs. Completion returns a generated AssetRef for ordinary asset_plan/asset_prepare; generation alone gives no physical pass.

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": {
      "recipe_id": "<recipe_id>",
      "parameters": "<parameters>"
    },
    "name": "asset_generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
recipe_idYes
parametersYes
request_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses that this is an asynchronous durable job, that only shipped fixed templates are permitted, that inputs are structured dimensions with no external programs, and that completion yields an AssetRef with no physical pass. It still omits polling/status mechanics, failure behavior, and any permission or runtime-configuration requirements.

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?

Three sentences, front-loaded with the action, with no filler or repetition. Dense domain jargon ('independent Sand3D runtime', 'physical pass') slightly limits readability but every sentence contributes a distinct constraint.

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 job-starting mutation with no annotations and no output schema, the description does supply the key return value (AssetRef) and the input restriction, which is the most important context. It falls short on the nested parameters contract and on how the durable job is tracked to completion, leaving real gaps for an agent to call it correctly.

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 two of three parameters are undocumented. The description does usefully constrain recipe_id to 'guide_plate_v1 or open_receiver_v1', but the nested 'parameters' object (additionalProperties: true, requiring 'structured dimensions') is left entirely unexplained, and request_id is never mentioned.

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 and resource: starting a durable job to generate an asset from a fixed shipped template, with the valid templates named inline. It also names the downstream consumers (asset_plan/asset_prepare), which helps place it relative to siblings, though it never contrasts with asset_acquire or asset_inspect.

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?

Usage is implied: use this when you need a generated AssetRef before planning or preparing, and note that 'generation alone gives no physical pass' so verification is still needed. However, there is no explicit when-to-use/when-not guidance versus the acquisition siblings, and no statement of prerequisites for the 'explicitly configured independent Sand3D runtime'.

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