Loading ToolBench
Discord Webhook MCP Server
Single tool with basic schema and Japanese description. Tool name 'send_message' lacks action clarity (send_to_where?). Description is 28 chars in Japanese, too short to guide LLM selection. Input schema present but parameters lack type constraints (no enums, ranges, or format specs). No output schema documented. Error handling returns text but lacks recovery guidance. No tool annotations. Composition is minimal (one tool only). Does not meet production baseline for parameter documentation or error classification.
Discordにメッセージを送信します
Tool description too short (28 chars in Japanese). LLMs cannot determine when to select this tool vs. other communication methods. Baseline: 194 chars average for A+ tools.
Tool name 'send_message' is ambiguous. Does not specify destination (Discord webhook). Should be 'send_discord_message' or 'post_to_discord_webhook' to clarify intent.
No output schema documented. LLM cannot predict response structure or plan downstream operations. Baseline: 100% of A+ tools document return types.
Error handling returns plain text without recovery guidance. 'Discord Webhook エラー: ...' does not tell LLM whether to retry, ask user, or abort. Should categorize as retryable vs. fatal.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 41 | 2026-07-28+ | v2 |
Parameters 'username' and 'avatar_url' lack descriptions in code (marked optional but no guidance on format, constraints, or when to use). Baseline: 100% of A+ tool params have descriptions.