Skip to main content
Glama

search_and_recolor

Identify a specific element in an image and change its color or appearance without affecting the rest.

Instructions

Recolor specific elements in an image.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesDescription of the scene
filenameNoOutput filename
image_pathYesPath to the image file
output_dirNoOverride output directory
select_promptYesWhat to select for recoloring
recolor_promptYesNew color/appearance for the selected element
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action without revealing whether a new file is created, how output paths are handled, or any side effects. This is a significant gap for a tool that modifies images.

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, direct sentence with no redundant wording. It front-loads the core action and resource, making it instantly scannable. Appropriately concise for the information it provides.

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?

The tool has 6 parameters and no output schema, yet the description is only one sentence. It fails to explain how the prompts interact, what the output is, or when to use this tool, leaving much of the context to be inferred. For a tool of this complexity, a richer description is needed.

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%, and each parameter has a clear description (e.g., 'What to select for recoloring' for select_prompt). The tool description adds no extra parameter semantics, so the baseline score of 3 applies.

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 'Recolor specific elements in an image.' states a specific action (recolor) and a clear resource (specific elements in an image), which distinguishes it from sibling tools like search_and_replace. It could be more explicit about how elements are selected, but the core purpose is clear.

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?

The description provides no guidance on when to use this tool versus alternatives such as style_transfer or search_and_replace. It does not mention exclusions, prerequisites, or typical scenarios, leaving the agent to infer usage from the name and schema.

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/Yaksh36/mcp-server-bedrock-image'

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