Skip to main content
Glama

paint_ground

Paint a polygon with a theme ground color using a 0-based color index and adjustable softness to feather edges for Wonderdraft map terrain edits.

Instructions

Paint theme ground colour number color_index (0-based) over a polygon, feathered by softness 0-1.

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": {
      "polygon": "<polygon>",
      "color_index": "<color_index>"
    },
    "name": "paint_ground"
  }
}

Input Schema

NameRequiredDescriptionDefault
polygonYes
softnessNo
color_indexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 burden, and it does disclose the meaningful behavior that the paint is feathered by softness, which is more than a restatement. It says nothing about whether the operation is reversible/undoable, permission or map-state requirements, or how the polygon is stamped, leaving real behavioral gaps for a 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no filler, which is good, but the phrasing 'theme ground colour number color_index' is awkward and redundant, and 'softness 0-1' reads as a fragment rather than a clear default/range statement.

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 three-parameter mutation tool with no annotations and no output schema, the definition omits the polygon format, where color indices come from (theme asset set?), and what the call returns or affects. An agent could guess, but could easily pass a malformed polygon or an out-of-range index.

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 description coverage is 0%, so the description must compensate, and it partly does: color_index is explicitly 0-based and softness is bounded 0-1 with feathered interpretation. However, polygon, the most complex required parameter, is left completely undefined as to coordinate space, point ordering, or minimum vertex count.

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: painting a theme ground colour index into a polygon region, with feathering. This is concrete enough that an agent knows it is a stylize/paint operation rather than a structural edit, though the sibling paint_land is never named as the nearby alternative to disambiguate land vs ground.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this versus paint_land or recolor/apply_theme, and no prerequisites such as needing an open map or a selected theme. The agent must infer selection context entirely from the tool name and siblings it is told not to reason about.

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