Skip to main content
Glama

replace_color

Replace every pixel matching a specified color with another color on a chosen layer and frame, with adjustable tolerance per channel.

Instructions

Replace every pixel matching from_color (within tolerance per channel) with to_color, on the chosen layer + frame.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
frameNo
layerNo
filenameYes
to_colorYes
toleranceNo
from_colorYes
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It states that the tool modifies pixels on the chosen layer and frame, but lacks details on side effects, undo behavior, or performance. It adds some context beyond annotations but is minimal.

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 a single, well-structured sentence with no unnecessary words. It conveys the essential functionality efficiently.

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?

With no annotations, no output schema, and 6 parameters, the description is too brief. It lacks guidance on when to use, prerequisites, input formats, and behavior under edge cases, leaving the agent underinformed.

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. It explains that from_color matching uses tolerance per channel, adding meaning beyond the schema. However, it does not elaborate on filename and frame parameters, leaving gaps.

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 clearly states the tool replaces pixels matching from_color with to_color, specifying tolerance and the target layer and frame. It uses a specific verb and resource, and distinguishes from sibling tools like fill_layer or draw_brush.

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 description implies usage for color replacement but provides no explicit guidance on when to use this tool vs alternatives, such as fill_area or draw_brush, or 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.

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/MalloyTheDev/aseprite-mcp'

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