Skip to main content
Glama
Sign In
text2d

text2d

by al3duc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

flood_fill

Replaces a contiguous area of matching pixels on a canvas with a new color, starting from a specified coordinate. Useful for recoloring shapes and regions in pixel art.

Instructions

Fills a contiguous area of matching color starting at (x, y).

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": {
      "canvas_id": "<canvas_id>",
      "x": "<x>",
      "y": "<y>",
      "color": "<color>"
    },
    "name": "flood_fill"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesStart X coordinate
yYesStart Y coordinate
colorYesFill color or palette index
canvas_idYesTarget canvas ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the disclosure burden; it does state that the operation modifies a contiguous matching-color region starting at (x, y). However, it omits behavior such as connectivity (4- vs 8-neighbor), out-of-bounds handling, and whether the canvas is mutated in place.

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?

A single, front-loaded sentence with no filler. Every word contributes to identifying the tool's behavior.

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?

The description plus fully described schema is sufficient for basic invocation, but the absence of annotations and output schema leaves connectivity and side-effect semantics undocumented. For a simple mutation tool these are meaningful gaps that the one-line description does not close.

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 100%, so the baseline is 3. The description adds little beyond the schema, only hinting that x/y are the start coordinates and that color is the replacement value; the schema already documents each parameter.

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?

The description names the tool's core operation ('Fills a contiguous area of matching color') and the starting point, which clearly identifies flood fill and distinguishes it from siblings like set_pixel or draw_shape. It is a specific verb+resource statement rather than a tautology.

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?

No explicit when-to-use or alternative routing is given, but the wording implies this tool is for filling a connected region of identical color, in contrast to setting individual pixels. There is no guidance on when not to use it.

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