Skip to main content
Glama

wb_radial_array

Create an XY radial array from a selected object, with the count including the source; previews by default and writes only when write=true.

Instructions

Create an XY radial array; count includes source. 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>",
      "count": "<count>"
    },
    "name": "wb_radial_array"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYes
pathYes
angleNo
countYes
writeNo
pivot_xNo
pivot_yNo
pivot_zNo
rotate_itemsNo
keep_noderefsNo
noderef_prefixNo

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?

No annotations are supplied, so the description carries the full burden. It usefully discloses two behaviors: count includes the source object, and the operation is a dry-run by default unless write=true (an important safety default). Beyond that it says nothing about what happens to existing geometry, how the pivot defaults, whether items are duplicated or moved, or what the call returns.

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 clauses with zero filler, and the destructive/write behavior is front-loaded after the purpose. It is arguably under-sized for an 11-parameter tool, but no sentence is wasted.

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 an 11-parameter mutation-capable tool with no annotations, no output schema, and zero schema descriptions, this description is far too thin. The two facts it does give are valuable, but the bulk of the contract an agent needs in order to call it correctly is missing.

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 the tool has 11 parameters, yet the description only explains count (includes source) and write (dry-run toggle). The nine remaining parameters — angle, pivot_x/y/z, rotate_items, keep_noderefs, noderef_prefix, file, path — get no meaning at all, so the agent must guess at angle defaults and noderef semantics.

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 (Create) plus the resource type (XY radial array), which separates it from the many sibling array/scatter tools such as wb_grid, wb_path_array, and wb_polygon_scatter. The only weakness is that 'XY radial' leaves the plane/pivot convention implicit.

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 dry-run/write=true clause tells the agent how to actually commit changes, which is real usage guidance. However, there is no guidance on when to pick this over wb_array, wb_path_array, or the scatter siblings, and no prerequisites are stated.

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