Qwen Max MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DASHSCOPE_API_KEY | Yes | Your Dashscope API key for accessing Qwen models |
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 |
|---|---|
| qwen_maxC | Generate text using Qwen Max model |
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 'qwen_max' has a clear and distinct purpose: generating text using the Qwen Max model.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'qwen_max' follows a single, consistent pattern with no deviations or mixing of conventions to evaluate.
A single tool is too few for most server purposes, as it severely limits functionality and scope. While it might suffice for a minimal text generation service, it lacks the breadth typically expected for an MCP server, making it feel thin and under-scoped.
The tool provides a basic text generation capability, but there are notable gaps for a comprehensive AI model server. For example, it lacks tools for managing models, handling different input formats, or performing other common AI tasks like classification or summarization, which limits its utility.