Loading ToolBench
A FastAPI-based server providing Gmail-like email tools via MCP protocol with SSE streaming
Critical failures across all dimensions. The single tool 'get_inbox_count' has an empty input schema ({}), no parameter descriptions, and a minimal description (58 chars). The tool is not properly registered in MCP format, it exists as a FastAPI endpoint, not an MCP tool definition. The /mcp SSE endpoint simulates tool definitions in event stream format rather than implementing the MCP protocol correctly. No error handling, no output schema documentation, no security controls (Gmail credentials not visible but likely hardcoded). This is a proof-of-concept, not a production MCP server.
Ritorna il numero di email non lette nella casella Gmail.
Empty input schema: tool 'get_inbox_count' has parameters={} with no type definitions or descriptions.
Tool not registered via MCP protocol: tool definitions are hardcoded in SSE event stream, not registered via MCP's tools/list or tools/call handlers. Cannot be discovered or invoked by standard MCP clients.
No output schema documented: tool returns {inbox: mail_count} but no schema is declared. LLMs cannot infer the structure or plan downstream calls.
No error handling or recovery guidance: tool has no try/catch, no validation, no error messages. If Gmail API fails or credentials are invalid, the LLM receives no actionable error.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 23 | 2026-07-28+ | v2 |
Credentials likely hardcoded or missing: no visible authentication mechanism. If Gmail credentials are embedded in the code, they will leak in logs and version control.