Family meal planning run by your own AI agent: weekly dinners, household votes, grocery list minus the pantry. Stdio MCP server for the hosted Agent Chef service.
Only 1 tool visible in source (get_members). Tool has empty input schema {} with no parameters documented. No description visible in server.js or test.mjs. Catalog is loaded from external catalog.json (not shown), so tool definitions cannot be verified from provided source. The test asserts 'every tool has annotations and an outputSchema' but this cannot be verified from the code provided. STDIO transport further limits protocol readiness.
Tool definitions loaded from external catalog.json (not provided in source). Cannot verify descriptions, parameter schemas, or output schemas.
get_members has empty input schema {}, no parameters documented.
No tool descriptions visible in server.js. Descriptions are critical for LLM tool selection.
Error handling in CallToolRequestSchema returns plain text errors without recovery guidance. 'Unknown tool', 'Could not reach', 'HTTP 401' lack actionable next steps for the LLM.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 32 | 2025-06-18+ | v2 |
API key required as environment variable (AGENT_CHEF_API_KEY). While not exposed as a tool parameter (good), the error message 'Agent Chef needs an API key' does not guide the LLM toward resolution or alternative auth paths.