SiliconFlow Flux MCP Server

generate_image

Generates an image from a text prompt using the Flux Schnell model. Provide a detailed English prompt and select a resolution.

Instructions

Generates an image using the SiliconFlow API with the Flux Schnell model (black-forest-labs/FLUX.1-schnell). Provide a detailed English prompt and select a resolution. Nya~ <3 重要提示：

此工具返回一个基础的 HTML <img> 标签（包含 src 和 alt）。
请在收到此标签后，为其添加一个 width 属性，值应在 200 到 500 像素之间（例如 width="300"）。
在最终回复用户时，请直接发送这个完整的、已添加 width 属性的 HTML <img> 标签，以便用户可以直接看到图片。

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>",
      "resolution": "<resolution>"
    },
    "name": "generate_image"
  }
}

Input Schema

Name	Required	Description
`prompt`	Yes	Required. The detailed text prompt for image generation. Please use English for best results, nya~!
`resolution`	Yes	Required. The desired image resolution.
`seed`	No	Optional. A specific seed for reproducibility. If omitted, a random seed is used.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 28, 2026

TDQS

A4.6/5.0

Behavior5/5

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

No annotations are provided, so the description fully carries the burden. It discloses that the tool returns an HTML img tag, specifies the model and API used, and instructs the agent to add a width attribute. No contradictions or hidden behaviors.

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 moderately concise, with clear structure in English followed by a Chinese note. The inclusion of 'Nya~ <3' is extraneous but does not hinder clarity. Could be slightly trimmed but remains effective.

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

Completeness5/5

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

Given no output schema, the description fully explains the return format (HTML img tag) and provides necessary post-processing instructions. It covers all essential aspects for an agent to use the tool correctly.

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?

Schema coverage is 100%, but the description adds value by recommending detailed English prompts and noting that seed is optional for reproducibility. This extra guidance enhances parameter understanding beyond the basic schema.

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 generates an image using the SiliconFlow API with the Flux Schnell model. It specifies the need for a detailed English prompt and resolution selection. The purpose is specific and well-defined.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

While no siblings exist, the description provides clear usage context: use English prompts, select resolution, and instructions for handling the returned HTML img tag (adding a width attribute). It implicitly guides when to use this tool for image generation.

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

generate_imageA