A Go web framework with MCP server capabilities for tool registration and dispatch
GoFastr exposes only one tool: ToolSearch. The tool has a reasonable description (95 chars) and a properly structured input schema with two parameters (query, limit). However, the schema lacks critical details: the query parameter has no type constraint (should be 'string'), limit lacks minimum/maximum bounds, and there is no documented output schema. The description does not explain what 'top-matching tools' means, how ranking works, or what fields are returned. Without output schema documentation, LLMs cannot plan downstream tool calls or extract results reliably. The tool is READ_ONLY (good), but the lack of output structure and parameter constraints significantly limits usability.
Discover tools available in this harness. Pass a query (a few words describing the capability you want, e.g. 'read file', 'spawn sub-agent', 'list directory'). Returns the top-matching tools with their schemas so you can call them directly. Use when you're unsure whether a capability exists or need a tool you don't see in your immediate context.
No output schema documented. LLMs cannot know what fields ToolSearch returns, preventing reliable downstream tool selection and data extraction.
Parameter 'limit' lacks minimum/maximum bounds. Unbounded integers let LLMs pass absurd values (e.g., limit=999999) that may break performance or API contracts.
Description does not explain ranking algorithm, result structure, or when to call ToolSearch vs. direct tool invocation. LLMs cannot determine when this discovery tool is necessary.
Only one tool exposed. A production MCP server should offer multiple domain-specific tools (e.g., if this is a web framework, tools for routing, middleware, templating, database operations). A single discovery tool is insufficient for agent autonomy.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 48 | 2026-07-28+ | v2 |
No error handling guidance. Description does not explain what happens if query matches no tools, or how the LLM should recover.