Single tool 'get_api_list' has critical definition gaps. Tool description is present but minimal (Chinese text, ~50 chars). Input schema is empty object {} with no parameters documented. No output schema is documented, LLMs cannot predict what fields to expect from the response. Tool lacks error handling guidance, parameter descriptions (none exist), and any indication of what the returned JSON structure contains. The hardcoded config file path (E:/workspace-yilai/...) and lack of validation expose security and portability issues. This server falls well below production baseline.
返回swagger api定义的接口一览
No output schema documented. LLMs cannot predict response structure (fields, types, nesting). Tool returns JSON.stringify(apiList) but LLMs have no way to know the shape.
Description is minimal (Chinese: '返回swagger api定义的接口一览', ~50 chars). Does not explain WHEN to use this tool, what prerequisites exist, or what the output contains. Below 10-1024 char baseline.
Hardcoded config file path 'E:/workspace-yilai/MCP-Servers/swagger-mcp-server/dist/config.json' is Windows-specific, non-portable, and a security risk. Should use environment variables or relative paths.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 29 | 2026-07-28+ | v2 |
Error handling returns plain text error messages in JSON response but does not guide LLM on recovery. E.g., 'Error: Failed to fetch swagger json: 404' gives no actionable next step.