cp77wb-mcp

Overview Schema Source Related Servers Discussions Admin

wb_live_surface_scatter

Create deterministic copies around a selected source and place them on the live scene surface. Preview the scatter by default; apply=true commits it, and one undo removes all copies.

Instructions

Create deterministic copies around one selected source and drop each copy onto the live scene surface; one undo removes the whole scatter. 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>",
      "count": "<count>"
    },
    "name": "wb_live_surface_scatter"
  }
}

Input Schema

Name	Required	Description	Default
`seed`	No
`apply`	No
`count`	Yes
`dir_x`	No
`dir_y`	No
`dir_z`	No
`half_x`	No
`half_y`	No
`half_z`	No
`rpc_dir`	Yes
`timeout`	No
`random_yaw`	No
`keep_noderefs`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Nov 9, 2026

TDQS

B3.3/5.0

Behavior4/5

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

With no annotations at all, the description carries the full burden and does disclose meaningful traits: determinism via seed, a non-destructive preview default, atomic undo grouping ('one undo removes the whole scatter'), and that it operates on a current selection. It doesn't cover failure behavior, timeout semantics, or whether the selection is consumed, which keeps it out of 5 territory.

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 dense sentences, front-loaded with the core action and followed by the safety/undo rule. No filler, though the terseness comes at the cost of the undocumented parameter block.

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?

A 13-parameter live-scene mutation tool with no annotations, no output schema, and 0% schema coverage demands far more explanation than two sentences. An agent can grasp the intent but cannot reliably supply the direction, half-extent, RNG, or noderef parameters without guessing.

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 13 parameters, so the description must compensate and largely doesn't. Only 'apply' and loosely 'seed'/'count' get implied meaning; dir_x/y/z, half_x/y/z, rpc_dir, timeout, random_yaw, and keep_noderefs are completely unexplained, including the required rpc_dir parameter.

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 states a specific verb and resource: create deterministic copies around one selected source and place them on the live scene surface. That distinguishes it reasonably from offline siblings like wb_scatter or wb_volume_scatter by the 'live scene surface' qualifier, though those siblings are never named, so the boundary requires inference.

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?

'Preview unless apply=true' gives a clear default-mode rule, which is useful context for when the tool mutates. However, there is no guidance on when to choose this over wb_scatter, wb_polygon_scatter, or wb_volume_scatter, nor on prerequisites such as requiring an existing selection.

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

Deploy Server