Skip to main content
Glama
Cuvara

game-art-mcp

by Cuvara

art.canvas.fill

Flood fill a contiguous pixel-art area with a hex color from a coordinate, enabling quick color updates in a 2D RPG game scene.

Instructions

Flood fill an area starting from a point.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYesStart X coordinate
yYesStart Y coordinate
colorYesFill color as hex string
session_idYesCanvas session ID
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It only describes the operation and does not mention side effects, color boundary behavior, whether pixels are replaced, whether the canvas is mutated immediately, 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.

Conciseness5/5

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

The description is one action-focused sentence with no filler words, and the core behavior is front-loaded. For a simple tool this is appropriately concise.

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 mutation-oriented canvas tool with no annotations and no output schema, the description omits important context such as return value, boundary interpretation, color matching behavior, and persistence/session effects. The agent must infer too much from the tool name and operation.

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 parameters are already documented. The description's phrase 'starting from a point' reinforces the x/y roles, but does not add meaning beyond the schema.

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 states a specific action, 'flood fill', a resource, 'an area', and the starting point. It is clearly distinguishable from sibling operations like art.canvas.set_pixel, art.canvas.draw_rect, and art.canvas.draw_line.

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 intended use is implied: fill a contiguous region from a starting coordinate. However, the description does not explicitly state when to choose this tool over alternatives, nor does it mention any exclusions or complementing tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Cuvara/game-art-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server