Loading ToolBench
Single tool with well-structured schema, clear naming, and good parameter descriptions. The tool definition is explicit and properly registered. However, the server lacks output schema documentation and error guidance, and the overall scope is minimal (1 tool). The tool itself is solid but the server's completeness is limited.
Send a notification to the user via Notifery. Use this to notify about task completions, errors, progress updates, or any event the user should know about.
No documented output schema. Tool description and code show the response is {success: true, message: 'Notification sent'} or an error, but this structure is not formally documented in the tool definition or visible to LLMs.
Error handling lacks recovery guidance. When the API fails, the tool throws a generic error message from the API response (via getErrorMessage()), but does not guide the LLM on retryability, root causes, or next steps (e.g., 'Check API key validity', 'Rate limit exceeded, wait 60s').
Parameter 'message' lacks minLength constraint. While maxLength is enforced (2048), there is no minimum length declared. This allows empty or whitespace-only messages, which may not be useful to users.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 9 | 2026-07-28+ | v2 |
| 2026-03-09 | C | 60 | - | v1 |
Parameter 'code' lacks enum constraint. The description says '0 = success, >0 = error' but does not specify valid ranges or standard HTTP/app status codes. LLMs may pass arbitrary numbers instead of recognizing standard codes like 200, 400, 500.
Parameter 'duration' lacks type and range constraints. Description says 'positive integer' but schema type is 'number' (allowing floats). No minimum or maximum declared. LLMs may pass negative or fractional values.
Parameter 'iconColor' validation is weak. Description mentions hex format example ('ff0000') but does not enforce format via regex or pattern. LLMs may pass invalid colors like 'red', '#ff0000', or 'rgb(255,0,0)'.
Server scope is extremely narrow. Only 1 tool (send_notification) with no discovery, list, or status check capabilities. Users cannot verify delivery, retrieve past notifications, or manage notification settings through this MCP server.