Well-curated 3-tool set with clear, focused purpose. Strong naming and schema design with typed parameters. Descriptions are adequate but could be more detailed about use cases and when to invoke each tool. The ask_question tool demonstrates sophisticated parameter handling (single repo or array of up to 10). No auto-generation patterns detected.
Ask any question about a GitHub repository and get an AI-powered, context-grounded response. Args: repoName: GitHub repository or list of repositories (max 10) in owner/repo format question: The question to ask about the repository
View documentation about a GitHub repository. Args: repoName: GitHub repository in owner/repo format (e.g. "facebook/react")
Get a list of documentation topics for a GitHub repository. Args: repoName: GitHub repository in owner/repo format (e.g. "facebook/react")
read_wiki_structure and read_wiki_contents have overlapping names and unclear differentiation. Documentation doesn't explain when to use 'structure' vs 'contents'.
Descriptions lack detail about output format and when an agent should prefer ask_question over direct wiki reading.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-03-24 | C | 67 | 2025-11-25 | v1 |