Loading ToolBench
The open-source event bus for AI agents. Webhooks in. Agent actions out.
AgentBus is NOT an MCP server, it is an event bus framework for AI agents. The single 'discord-handler' tool is a handler component, not an MCP tool definition. No MCP protocol implementation is visible in the source. The tool has a reasonable description (95 chars) and input schema with 6 parameters, but the schema lacks type definitions for array items (mentionRoles, eventFilter), parameter descriptions are minimal or absent (webhookUrl, username, avatarUrl lack descriptions), and there is no output schema documented. The tool is not registered via MCP's tool registration mechanism, it appears to be a configuration-driven handler. This is a fundamental mismatch: AgentBus is a webhook event bus, not an MCP server.
Create a Discord notification handler for AgentBus. Acts as a notification sink -- subscribes to all events (pattern `**`) and posts formatted embed messages to a Discord webhook URL. Use `eventFilter` in the config to limit which events trigger notifications.
Not an MCP server. AgentBus is an event bus framework, not an MCP protocol implementation. No MCP tool registration, no protocol transport, no stateless request handling.
Input schema lacks type definitions for array parameters. 'mentionRoles' and 'eventFilter' are declared as arrays but have no 'items' schema specifying element types.
Parameter descriptions missing or incomplete. 'webhookUrl', 'username', 'avatarUrl' have no descriptions. LLMs cannot infer parameter meaning from names alone.
No output schema documented. Callers cannot know what the handler returns or what fields to expect for downstream composition.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 31 | 2026-07-28+ | v2 |
No error handling guidance. Tool description does not explain failure modes, recovery steps, or what to do if the Discord webhook is invalid or unreachable.