Skip to main content
Glama

outpaint

Extend an image outward in any direction by generating new content that matches the original scene, preserving visual consistency for larger compositions.

Instructions

Extend an image in any direction while maintaining visual consistency.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNoPixels to extend top
leftNoPixels to extend left
rightNoPixels to extend right
bottomNoPixels to extend bottom
promptYesDescription for the extended area
filenameNoOutput filename
image_pathYesPath to the image file
output_dirNoOverride output directory
Behavior2/5

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

With no annotations, the description bears full responsibility for behavioral disclosure. It only mentions 'maintaining visual consistency' as a quality, but says nothing about side effects, whether the original image is modified, output file handling, or any limitations. This is too minimal to understand the tool's behavior.

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 a single, efficient sentence that is front-loaded with the key action. It is concise and contains no filler, though it may be slightly under-sized for a tool with many parameters, the wording itself is well-structured.

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 8 parameters, no output schema, and no annotations, yet the description provides no context about return values, side effects, or operational details. It is incomplete for a tool of this complexity, leaving the agent without crucial information.

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?

The input schema provides full documentation for all 8 parameters with descriptions, so the schema already covers parameter semantics. The description adds no extra meaning beyond what the schema provides, hence a baseline score of 3.

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's function: 'Extend an image in any direction while maintaining visual consistency.' This is a specific verb+resource combination that distinguishes outpaint from sibling tools like upscale or style transfer.

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?

No when-to-use or alternative guidance is provided. The description merely states what the tool does, leaving the agent to infer when to choose it over other image manipulation tools. It does not mention exclusions or contexts where another tool would be preferred.

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