Skip to main content
Glama

wb_live_spawn_asset

Spawn an exact indexed WB asset into the active editor, with optional camera placement and surface snapping. Preview changes by default; set apply=true to commit.

Instructions

Spawn one exact indexed WB asset directly into the active editor, optionally in front of the camera and dropped to the surface. Preview unless apply=true.

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": {
      "rpc_dir": "<rpc_dir>",
      "catalog": "<catalog>",
      "asset": "<asset>"
    },
    "name": "wb_live_spawn_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
zNo
yawNo
nameNo
rollNo
applyNo
assetYes
pitchNo
moduleNo
parentNo
catalogYes
rpc_dirYes
timeoutNo
variantNo
distanceNo
placementNo
snap_to_surfaceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden, and its main contribution is disclosing that the operation is dry-run by default and only mutates with apply=true. Beyond that it says nothing about what state the spawn touches (selection, undo history, parent hierarchy), how 'placement' modes differ, or what a preview returns — significant gaps for an 18-parameter mutating tool.

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?

Two tight sentences, with the core action and the key scope constraint front-loaded and the safety default last. No filler, though the brevity is partly achieved by omitting information the agent actually needs.

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

Completeness2/5

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

For a tool with 18 properties, zero schema coverage, no annotations and no output schema, the description is far too thin to call correctly without guessing. It conveys the headline action and the dry-run flag but leaves most parameter semantics and all behavioral side effects undocumented.

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 description must explain 18 parameters and instead only gestures at three concepts: camera-relative placement, surface snapping, and apply. The enum parameter placement (serialized/camera/player), parent, module, variant, name, distance, timeout, and the x/y/z/yaw/pitch/roll coordinates are all left entirely unexplained.

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 ("Spawn one exact indexed WB asset directly into the active editor") with a scope qualifier ("one exact indexed") that hints at the difference from bulk siblings like wb_asset_pool_spawn. It never names the nearest sibling, wb_spawn_asset, so an agent must still infer which spawn tool to use.

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?

The clause "Preview unless apply=true" gives real guidance on the safe default path. There is no guidance on when to choose this over wb_spawn_asset, wb_asset_pool_spawn, or wb_live_surface_scatter, and no prerequisites for the catalog/rpc_dir requirements.

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

Deploy Server

Other Tools