Skip to main content
Glama

wb_polygon_scatter

Scatter copies deterministically inside an XY polygon with optional seed for repeatable placement; previews by default and writes only when write=true.

Instructions

Deterministically scatter copies inside an XY polygon. Dry-run unless write=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": {
      "file": "<file>",
      "path": "<path>",
      "points": "<points>",
      "count": "<count>"
    },
    "name": "wb_polygon_scatter"
  }
}

Input Schema

NameRequiredDescriptionDefault
zNo
fileYes
pathYes
seedNo
countYes
writeNo
pointsYes
z_jitterNo
scale_maxNo
scale_minNo
random_yawNo
create_scaleNo
keep_noderefsNo
noderef_prefixNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

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 full behavioral burden; it does disclose two meaningful traits: the non-mutating default (dry-run) and deterministic output (implying seed reproducibility). Nothing is said about what the returned dry-run payload looks like, what happens to existing scene nodes, or how noderef handling works, which matters for a 14-parameter mutation tool.

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?

Two short sentences with the core action first and the safety-relevant default second. No filler, no redundancy, front-loaded.

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 14 parameters, zero schema descriptions, no annotations, and no output schema, two sentences are far from sufficient. An agent cannot determine what file/path identify, what the scale and yaw options do, or how the dry-run result is reported before committing to a call.

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 14 parameters, so the description must compensate and it does not. Only points (polygon), write, and implicitly seed/count are traceable to the text; z, z_jitter, scale_min, scale_max, create_scale, random_yaw, keep_noderefs, noderef_prefix, file, and path are entirely opaque, and several are non-obvious (keep_noderefs).

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?

"Deterministically scatter copies inside an XY polygon" names a specific verb (scatter), resource (copies), and spatial constraint (XY polygon), which separates it from wb_volume_scatter by dimension and from wb_path_array/wb_grid by placement strategy. It never names those siblings, so the differentiation is inferable from the name rather than stated.

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?

"Dry-run unless write=true" is a genuinely useful default-mode instruction that tells the agent how to preview safely. However, there is no guidance on when to pick this over wb_scatter, wb_volume_scatter, wb_asset_pool_spawn, or wb_live_surface_scatter, all of which could plausibly place copies.

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