Skip to main content
Glama
Sign In
GoldBean

GoldBean

by wuzenghai616-lang
OverviewSchemaSourceRelated ServersDiscussions(4)Admin
JavaScript
Remote

baidu_image_gen

Generate AI images from text prompts using the Qwen-Image model, with support for multiple images per request.

Instructions

[Image] AI图片生成（Qwen-Image） — $0.05/call (free: 5/5 today)

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>",
      "n": "<n>"
    },
    "name": "baidu_image_gen"
  }
}

Input Schema

NameRequiredDescriptionDefault
nYes生成数量(可选, 默认1)
promptYes图像描述

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

The description only discloses the cost ($0.05/call) and free usage count (5/5 today), but lacks behavioral details such as that the tool generates images from text prompts, aspects of the generation process, or limitations. With no annotations, the description should cover more behavioral aspects.

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 very concise, consisting of a single phrase and pricing info. It is front-loaded with the purpose. However, the pricing might be considered metadata rather than behavioral guidance. Overall, no unnecessary words.

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?

Given the simple tool (2 parameters, no output schema, no annotations), the description is incomplete. It does not explain the return format, how the generation works, or any usage notes. The agent would need to infer from the schema.

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?

The input schema already describes both parameters (prompt and n) with 100% coverage. The description adds no additional explanation or examples beyond the schema, meeting the baseline for high schema coverage.

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 'AI图片生成（Qwen-Image）' clearly indicates the tool generates images using the Qwen-Image model, distinguishing it from image editing (baidu_image_edit) and video generation (baidu_video_gen) siblings. However, it could be more explicit about the text-to-image functionality.

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 like baidu_image_edit or baidu_vision_chat. There is no mention of use cases, prerequisites, or caveats.

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