A Model Context Protocol server with SiliconFlow Flux that generates images using the black-forest-labs/FLUX.1-schnell model.
Single tool with valid schema and reasonable description, but several quality gaps. The tool name is correctly verb-prefixed ('generate_image'), input schema is present with proper types and enums, and the core description exists. However, the description contains mixed-language instructions (English + Chinese) directed at the LLM rather than documenting tool behavior, parameter descriptions are present but vary in quality, and no output schema is documented. The tool lacks error handling guidance, and the instruction to the LLM about adding HTML width attributes is an anti-pattern (tool descriptions should document behavior, not instruct the caller). Parameter documentation is adequate but the seed parameter's 'Optional' note in the description is redundant with not being in 'required'.
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 重要提示: 1. 此工具返回一个基础的 HTML `<img>` 标签(包含 src 和 alt)。 2. 请在收到此标签后,为其添加一个 `width` 属性,值应在 200 到 500 像素之间(例如 `width="300"`)。 3. 在最终回复用户时,请直接发送这个*完整的*、已添加 `width` 属性的 HTML `<img>` 标签,以便用户可以直接看到图片。
Tool description contains instructions to the LLM (add width attribute to HTML) rather than documenting what the tool does and returns. Descriptions should state WHAT the tool does, not HOW the caller should process results.
No output schema documented. The tool returns an HTML img tag and cached metadata (according to code), but the description does not specify the response structure. LLMs cannot plan downstream operations without knowing return fields.
Mixed-language description (English + Chinese) with colloquial markers ('Nya~ <3', '主人', '喵'). While culturally consistent with the codebase, the description should prioritize clarity for LLM parsing. Chinese instructions about HTML handling are hard for English-trained LLMs to process and act on.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | C | 65 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 40 | - | v1 |
No error handling guidance. The description does not explain what happens on failure (e.g., invalid API key, rate limit, invalid prompt). Per the rubric, errors should guide the LLM on recovery steps.
API key exposed in server-side code via environment variable (SILICONFLOW_API_KEY). While not a parameter (good), the server throws a startup error if missing. No guidance on secure key rotation or credential management.