Skip to main content
Glama
Sign In
Flux Cloudflare MCP

Flux Cloudflare MCP

by duoduoriver
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

generate_image

Transform text prompts into custom images using the Flux model. Specify dimensions, aspect ratio, and save location for high-quality outputs with controlled denoising steps.

Instructions

Generate an image from a text prompt using Flux model

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prompt": "<prompt>"
    },
    "name": "generate_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
aspect_ratioNoAspect ratio for the generated image1:1
file_nameNoName of the file to save the image
heightNoHeight of the generated image
num_inference_stepsNoNumber of denoising steps. 4 is recommended, and lower number of steps produce lower quality outputs, faster.
promptYesPrompt for generated image
save_folderNoFolder path to save the image./output
widthNoWidth of the generated image

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the model ('Flux') but doesn't cover important traits like rate limits, authentication needs, quality expectations, error handling, or what happens after generation (e.g., file saving behavior). The description is minimal and leaves critical operational details unspecified.

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, efficient sentence with zero wasted words. It's appropriately sized and front-loaded with the core functionality. 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?

For a complex image generation tool with 7 parameters and no output schema, the description is inadequate. It lacks information about return values (e.g., file path, success indicators), error conditions, model limitations, or usage examples. With no annotations and rich parameter schema, the description should provide more context to guide effective use.

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%, so the schema fully documents all 7 parameters. The description adds no parameter-specific information beyond what's in the schema (e.g., it doesn't explain prompt best practices or aspect ratio implications). Baseline 3 is appropriate when schema does all the work.

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 verb ('Generate') and resource ('image') with the method ('from a text prompt using Flux model'). It's specific about the action and technology used. However, without sibling tools, we can't assess differentiation, so it can't achieve a perfect 5.

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, prerequisites, or constraints. It simply states what the tool does without context for decision-making. No sibling tools exist, but general usage context is missing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools

Related Tools