Agentic tool use via the Model Context Protocol: exposes Project 1 and Project 2 as standardized MCP tools, and an agent that discovers and calls them dynamically instead of hardcoded integrations.
Two tools with basic schemas and descriptions, but significant gaps in parameter documentation and output structure. ask_httpx_assistant has a single string parameter with minimal context; get_eval_quality_summary has no parameters but lacks output schema documentation. Neither tool documents what fields the LLM should expect in responses, forcing the agent to parse unstructured text. Descriptions are present but generic (10 - 20 words), below the 50 - 200 char LLM-optimized baseline. No error handling guidance, no parameter constraints, no output schema declarations.
Ask a question about the httpx Python HTTP library (its source code and documentation) and get a grounded, cited answer.
Get the most recent automated quality evaluation of the httpx Q&A assistant - faithfulness, relevancy, groundedness, and refusal accuracy scores from the latest test run.
No output schema documentation. Both tools return free-form strings; LLM cannot parse structured fields or plan downstream calls. ask_httpx_assistant returns answer + sources as concatenated text; get_eval_quality_summary returns formatted metrics as a single string.
Parameter descriptions missing or insufficient. ask_httpx_assistant's 'question' parameter has a 10-word description; no guidance on expected format, length, or scope (e.g., 'httpx library only, or broader Python HTTP?'). get_eval_quality_summary has no parameters but lacks output field documentation.
No error handling or recovery guidance. If RAG_API_URL or EVAL_API_URL are misconfigured, or if the upstream service is down, the tools return raw HTTP errors (response.raise_for_status()). LLM receives no actionable guidance on what to do next.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 56 | 2026-07-28+ | v2 |
Tool descriptions are generic and under 50 characters. 'Ask a question about the httpx Python HTTP library...' (18 words) does not explain WHEN to use this tool vs. other sources, what quality to expect, or prerequisites. Baseline for LLM-optimized descriptions is 50 - 200 chars.
No pagination or result limits documented. ask_httpx_assistant may return arbitrarily long answers; no guidance on max length, truncation, or how to request summaries. get_eval_quality_summary returns only the latest run, no way to access historical data or filter by date range.