Skip to main content
Glama

generative_fill

Fill or replace areas in images using a text prompt. Provide an image, mask, and prompt to generate new content in the masked region.

Instructions

Generative fill / inpaint with prompt

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of variations to generate.
promptYesText description of what to generate in the masked area.
mask_urlNoURL of the mask image (white = fill area).
image_urlYesURL of the source image.
mask_base64NoBase64-encoded mask image (alternative to mask_url).
negative_promptNoWhat to avoid in the generated content.
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not mention that the tool modifies images, requires a mask, or any side effects. Schema provides parameter details but not behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is very concise, consisting of a single phrase that front-loads the purpose. While it is not structured, it is efficient and contains no unnecessary words.

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?

Given the complexity of a generative tool with 6 parameters and no output schema, the description is too minimal. It does not explain what the output is, how the mask works, or provide any example usage.

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 100%, so each parameter already has a description. The tool description adds no extra meaning beyond the schema, meeting the baseline of 3.

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 clearly states the tool performs generative fill/inpainting with a prompt. However, it does not distinguish from sibling tools like 'magic_inpaint' or 'image_outpainting', which have similar functionality.

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, nor does it mention prerequisites or appropriate contexts.

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/celeryhq/simplified-mcp-server'

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