MCP server that provides access to Alibaba's Qwen Max language model via the DashScope API
Single tool 'qwen_max' has a complete input schema with proper types and constraints (temperature 0-2, max_tokens default 8192). Description is present but generic (28 chars: 'Generate text using Qwen Max model'). Parameter descriptions are adequate but lack context on when/why to use the tool. No output schema documented. No error recovery guidance. Tool name lacks action verb prefix (should be 'generate_text_qwen_max' or similar). No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Composition is minimal, single tool with no chaining support.
Generate text using Qwen Max model
Tool name 'qwen_max' lacks action verb prefix. Should start with verb (e.g., 'generate_text', 'complete_prompt') to help LLMs infer intent from name alone.
Tool description is too short (28 chars) and lacks context. Does not explain WHEN to use this tool vs alternatives, what it returns, or prerequisites. Should be 50-200 chars with actionable guidance.
No output schema documented. LLMs cannot plan downstream operations or extract structured data. Must document return type (e.g., {type: 'text', text: string}).
Error handling returns generic McpError with API error message. Does not guide LLM on recovery (e.g., 'API rate limited, retry in 60s' or 'Invalid API key, check DASHSCOPE_API_KEY environment variable').
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 50 | 2026-07-28+ | v2 |
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). This tool is read-only and idempotent, should declare these hints for agent planning.