Skip to main content
Glama

scatter

Fill a rectangular region with a character at a controlled density from 0 to 1, using only empty cells to add stars, stippling, grain, or organic texture over existing ASCII art.

Instructions

Scatter a character across a region with a density from 0 to 1. Great for stars, stippling, grain, and organic texture. Only empty cells are filled, so it layers over existing art.

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": {
      "x": "<x>",
      "y": "<y>",
      "width": "<width>",
      "height": "<height>"
    },
    "name": "scatter"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
charNo.
widthYes
heightYes
densityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden, and it does surface the most surprising trait here: only empty cells are filled, making it non-destructive over existing art. It does not state whether output is random/non-deterministic, what it returns, or that it mutates the canvas, which are material for a drawing 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?

Three short sentences with no filler: the mechanism is stated first, the use cases second, and the critical collision rule last. Every sentence adds information an agent needs.

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

Completeness3/5

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

For a six-parameter mutation tool with no annotations and no output schema, the description covers purpose, use cases, density semantics, and collision behavior reasonably well. It still leaves parameter conventions and return/randomness behavior unaddressed, so it is adequate rather than complete.

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

Parameters3/5

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

Schema coverage is 0%, so the description must compensate for all six parameters; it does clarify that density is a 0-1 fraction and that the region is bounded, and mentions the character being scattered. It leaves x/y coordinate conventions, the char default of '.', and the 1-400 width/height limits entirely to the schema.

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 opens with a specific verb+resource+effect combination: scatter a character across a region with a 0-1 density. It also implicitly distinguishes itself from solid-fill siblings by noting that only empty cells are filled, though it never names an alternative tool.

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?

It offers concrete use cases (stars, stippling, grain, organic texture) and a layering constraint, which implies when this is preferable to a fill or draw operation. However, there is no explicit when-not guidance or named alternative, so the agent must infer the boundary.

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