Skip to main content
Glama

scatter_symbols

Places symbols inside a polygon using Poisson-disk sampling; set density, scale, seed, and land-only filtering, then get placed IDs and dropped-sample counts.

Instructions

Scatter symbols (Poisson-disk) inside a polygon. density is symbols per 100x100 px of area (min_spacing in px, default from the set's radius, may lower the count). scale multiplies the set's base size. Returns the placed ids and how many samples were dropped (off-map, or on water with land_only).

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": {
      "set_key": "<set_key>",
      "polygon": "<polygon>",
      "density": "<density>"
    },
    "name": "scatter_symbols"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNoRandom seed (0 to 2^32-1); the same seed gives the same result.
scaleNo
densityYes
polygonYes
set_keyYes
land_onlyNo
min_spacingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/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 does well: it names the algorithm, explains that min_spacing can reduce the realized count, that scale multiplies base size, and that the tool reports dropped samples for off-map and land_only water rejections. It does not say whether placements are additive to or replacing existing objects, or whether the operation is undoable, which is the main remaining behavioral gap.

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?

Three dense sentences, no filler, with the core operation and algorithm front-loaded and the return-value note last. Every clause conveys operational information the agent cannot get from the schema.

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

Completeness5/5

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

For a 7-parameter generation tool with no annotations and no output schema, the description covers the algorithm, the three tuning parameters' units and interactions, the land_only filter, and the return payload (placed ids plus dropped-sample count). The only unstated item, additivity versus replacement of existing objects, is minor relative to the coverage provided.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 14% (only seed is documented in the schema), so the description must compensate, and it does: density units (symbols per 100x100 px), min_spacing units and default source (set radius) with its count-lowering effect, scale's multiplicative meaning, polygon as the containment region, land_only's effect on water samples, and set_key's role via 'the set's radius'/'base size'. Only set_key's exact expected string form is left implicit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Scatter symbols ... inside a polygon') plus the underlying algorithm (Poisson-disk), which is unmistakably different from the single-object sibling add_symbol or the mutate-in-place sibling recolor_symbols. An agent knows exactly what operation this performs without opening the schema.

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 by the polygon-scoped, density-driven semantics, so an agent can infer this is the multi-symbol placement tool. However, there is no explicit when-to-use or when-not guidance and no named alternative (e.g. add_symbol for a single placement), leaving selection to inference.

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