Skip to main content
Glama

generate_image

Create images from text prompts with support for variations, character consistency, and real-world grounding. Adjust quality, aspect ratio, and purpose for tailored results.

Instructions

Generate image with specified prompt and optional parameters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesThe prompt for image generation (English recommended for optimal structured prompt enhancement)
fileNameNoCustom file name for the output image. Auto-generated if not specified.
inputImagePathNoOptional absolute path to source image for image-to-image generation. Use when generating variations, style transfers, or similar images based on an existing image (must be an absolute path)
blendImagesNoEnable multi-image blending for combining multiple visual elements naturally. Use when prompt mentions multiple subjects or composite scenes
maintainCharacterConsistencyNoMaintain character appearance consistency. Enable when generating same character in different poses/scenes
useWorldKnowledgeNoUse real-world knowledge for accurate context. Enable for historical figures, landmarks, or factual scenarios
useGoogleSearchNoEnable Google Search grounding to access real-time web information for factually accurate image generation. Use when prompt requires current or time-sensitive data that may have changed since the model's knowledge cutoff. Leave disabled for creative, fictional, historical, or timeless content.
aspectRatioNoAspect ratio for the generated image
imageSizeNoImage resolution for high-quality output. Specify "1K", "2K", or "4K" when you need specific resolution. Leave unspecified for standard quality.
purposeNoIntended use for the image (e.g., cookbook cover, social media post, presentation slide). Influences lighting, composition, and detail level to match the context.
qualityNoQuality preset controlling speed/fidelity tradeoff. Only specify when the user explicitly requests a specific quality level; omit to use the server's configured default. "fast": best for drafts and rapid iteration. "balanced": better detail and coherence, moderate latency. "quality": highest fidelity, use for final deliverables where quality matters most.
Behavior2/5

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

No annotations exist, so the description must bear full burden for behavioral disclosure. It only states 'Generate image' without revealing any side effects, output format, rate limits, or content restrictions. The absence of such information makes the tool behaviorally opaque.

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?

One sentence, zero wasted words, and immediately communicates the core function. It is optimally concise and front-loaded. Every word earns its place.

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?

Despite the complexity (11 parameters, no output schema, no annotations), the description fails to explain the return type, output handling, or any operational context. The schema descriptions are detailed, but the overall tool description is incomplete for an agent to understand the full lifecycle of image generation.

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?

With 100% schema description coverage, each parameter already has meaningful description. The tool's description adds 'with specified prompt and optional parameters' but no additional semantic value beyond the schema. Baseline 3 is appropriate as the description neither enhances nor detracts from parameter understanding.

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 action ('Generate image') and resource ('with specified prompt and optional parameters'). It is specific, differentiating from any potential sibling tools (none present), and leaves no ambiguity about the primary function.

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 (though no siblings exist) nor any context-specific advice. It lacks instructions on when particular parameters (like blendImages or useGoogleSearch) are appropriate, leaving the agent without strategic direction.

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/shinpr/mcp-image'

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