ModelScope Image MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MODELSCOPE_API_KEY | Yes | Your ModelScope API key for accessing the Qwen-Image model |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_imageC | 使用ModelScope生成图片 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The single tool 'generate_image' has a clearly distinct purpose that cannot be confused with any other tools in the set.
With only one tool, naming consistency is inherently perfect. The tool name 'generate_image' follows a clear verb_noun pattern, and there are no other tools to create inconsistency with.
A single tool for an image generation server is too minimal for the apparent scope. While image generation is a core function, typical image-related servers would include additional tools for variations, editing, or management tasks, making this feel incomplete.
The server is severely incomplete for an image generation domain. It only provides generation with no tools for editing images, creating variations, managing generated content, or handling different parameters or styles, which are common in such systems.