sensenova-u1-mcp

generate_image

Generates images from text prompts using SenseNova U1 Fast. Supports Chinese prompts, multiple size options, and batch creation of up to 4 images per request.

Instructions

使用 SenseNova U1 Fast 模型，根据文本描述生成图像。支持中文 prompt，返回临时 URL 请及时下载。

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

Name	Required	Description	Default
`n`	No	生成数量，1~4 张。
`size`	No	图像分辨率，支持 11 种尺寸。默认 2752x1536(16:9)。	2752x1536
`prompt`	Yes	图像描述文本，支持中文。描述越详细（构图、色彩、风格、元素）效果越好。最大约 4096 token。

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.4Jul 31, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It usefully notes that the returned URL is temporary and should be downloaded promptly, and that Chinese prompts are supported. However, it does not mention potential costs, latency, or error behavior, which would be valuable for full transparency.

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 two concise sentences, front-loaded with the core function and followed by important caveat. Every word earns its place; no wasted text.

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 simple three-parameter tool with a rich schema and no output schema, the description effectively covers the critical behavioral aspect (temporary URL) and language support. It is sufficiently complete for an agent to invoke the tool, though it could mention the range of 'n' or available sizes, but the schema already handles that.

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 baseline is 3. The description adds minor reinforcement (e.g., supports Chinese prompts) but does not explain parameters beyond what the schema already provides. This is acceptable given the schema's completeness.

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 it generates images from text descriptions using a specific model (SenseNova U1 Fast). The verb+resource (generate image) is specific and unambiguous, even though no siblings are present to differentiate.

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?

No guidance is provided on when to use this tool versus alternatives, nor any exclusions or prerequisites. It simply states what the tool does, leaving the agent to infer usage from the tool's existence.

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