Loading ToolBench
Icarus CDK is a framework for building MCP servers, not an MCP server itself. The 6 tools shown are template examples and test fixtures, not registered in a functional MCP server. Transport mechanism is unknown/not implemented. Tool definitions lack output schemas entirely. Descriptions are present but minimal (10-50 chars). Input schemas are visible for most tools but sparse. No error handling guidance, no tool annotations, no pagination support. The codebase demonstrates macro-based tool registration infrastructure but does not constitute a production-ready MCP server.
Basic tool function that should compile successfully
Get the current Bitcoin price in USD.
Get geographic information for an IP address.
Tool function with string parameters
Health check for HTTP outcalls
Public tool
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract return values without knowing the response structure.
Descriptions are too short (10-50 chars). Rubric requires 10-1024 chars, with baseline ~194 chars. Current descriptions lack WHEN to use the tool and what it returns.
Tool 'public_tool' has a vague, non-descriptive name that conveys no action or purpose. Names must start with action verbs (get_, create_, update_, delete_, search_).
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 39 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 29 | - | v1 |
No error handling guidance. Tools do not indicate what happens on failure (network error, invalid IP, missing BTC price feed), how to retry, or what the LLM should do next.
No parameter descriptions for 'ip' in get_ip_info. Rubric requires every parameter to have a non-empty description explaining what it controls.
This is a framework/CDK, not a deployed MCP server. The tools shown are templates and test fixtures. No actual transport (HTTP, STDIO, SSE) is configured or functional.