Loading ToolBench
A Spring Boot-based MCP server that provides notification capabilities through a simple notification tool
Single tool 'notify' with minimal definition quality. Tool name lacks action clarity (should be 'send_notification'). Description is extremely brief (24 chars, below 34-char p10 baseline). Input schema present but parameter description is generic. No output schema documented. No error handling guidance. No parameter constraints or validation hints. Tool appears functional but falls well below production standards for LLM-driven agent use.
Send notification message
Tool name 'notify' lacks action verb clarity. Should be 'send_notification' to help LLMs infer intent from the name alone.
Tool description is 24 characters ('Send notification message'), below p10 baseline of 34 chars. Lacks context on WHEN to use, WHAT it returns, and any prerequisites. LLMs cannot determine selection criteria.
No output schema documented. LLMs cannot plan downstream tool calls or extract structured data from the response. Current code returns a plain string.
Parameter 'message' has generic description ('Notification Message'). No constraints on length, format, or content. No guidance on what happens if message is empty or exceeds limits.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 37 | <=2025-11-25 | v2 |
No error handling guidance. Tool logs but does not document failure modes (e.g., what if notification service is down?). LLMs receive no recovery hints.