Skip to main content
Glama

flux_text_to_image

Generate images from text prompts using local Flux models. Auto-detects installed models to produce 1024x1024 images.

Instructions

Generate images using Flux (local model).

All parameters except prompt are optional with sensible defaults. Auto-detects installed Flux model (GGUF or safetensors) and CLIP encoders. Produces high-quality 1024x1024 images by default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seedNoRandom seed. Default: -1 (random).
stepsNoSampling steps. Default: 20. Typical: 15-30.
widthNoImage width in pixels. Default: 1024. Must be multiple of 16.
heightNoImage height in pixels. Default: 1024. Must be multiple of 16.
promptYesText description of the desired image.
guidanceNoPrompt guidance strength. Default: 3.5. Typical: 2.0-5.0. Note: Flux embeds guidance in conditioning, not in CFG.
vae_nameNoVAE model. Default: "ae.safetensors". Use list_models(folder="vae") to see options.ae.safetensors
batch_sizeNoNumber of images to generate. Default: 1.
clip_name1NoFirst CLIP model (clip_l). Default: "" (auto-detects).
clip_name2NoSecond CLIP model (t5xxl). Default: "" (auto-detects).
diffusion_modelNoFlux model filename. Default: "" (auto-detects). Supports both safetensors and GGUF formats. Use list_models(folder="diffusion_models") to see options.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses key behaviors: local model execution, auto-detection of Flux model and CLIP encoders, and default 1024x1024 high-quality output. It does not mention potential runtime costs or failure modes, but the main behavioral traits are conveyed.

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 three short sentences with no fluff. Each sentence earns its place: purpose, parameter flexibility, and default behavior. It is front-loaded and easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a text-to-image tool with an output schema, the description covers the essential operational context: local model, defaults, auto-detection, and output size. It could be more complete with explicit guidance on when to use this versus sibling generation tools, but overall it is sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents all 11 parameters with high coverage, so the baseline is 3. The description adds meaningful high-level semantics by stating that only prompt is required and all other parameters have sensible defaults, while also explaining auto-detection behavior for model-related parameters.

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 opens with 'Generate images using Flux (local model)', which is a specific verb plus a clearly named resource. It distinguishes this tool from siblings like text_to_image by specifying Flux and local execution.

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 through 'All parameters except prompt are optional with sensible defaults' and 'Auto-detects installed Flux model', but it never explicitly states when to choose this tool over alternative image generation tools. No exclusions or alternative tool mentions are provided.

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/halbert04/comfyui-mcp'

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