MCP server that provides AI model recommendations based on natural language descriptions of use cases
Single tool 'recommend_models' has a basic schema with one string parameter, but lacks depth in descriptions and error guidance. The tool description (54 chars) is below the 194-char baseline and doesn't explain WHEN to use it or what makes it distinct. Parameter description is adequate (72 chars, at baseline) but generic. No output schema is documented, LLMs cannot predict the structure of recommendations. Error handling returns plain text rather than structured guidance. No tool annotations (readOnlyHint, etc.). Overall: functional but minimal quality.
Natural language description of what you want to build or do with an AI model
Tool description is 54 characters, below 194-char baseline. Does not explain WHEN to call this tool, what makes it distinct from other model-selection tools, or what output structure to expect.
No output schema documented. LLMs cannot predict the structure of the recommendation response (fields: model_id, rank, reasoning, cost_estimate, tradeoffs, dataset_age_hours). This forces the LLM to parse unstructured JSON and risks misinterpretation.
Error handling returns plain-text error messages without recovery guidance. E.g., 'Error: ANTHROPIC_API_KEY environment variable is required' does not tell the LLM what to do next or whether the error is retryable.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). The tool is read-only and idempotent, but the LLM has no explicit signal of this, it must infer from the name and description.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 46 | 2026-07-28+ | v2 |
Tool name 'recommend_models' is generic and does not clearly distinguish this from other model-recommendation or model-search tools. A more specific name like 'search_ai_models_by_usecase' or 'get_model_recommendations' would improve clarity.