27 tools with complete schemas and descriptions. Naming follows verb_noun convention well (create_, get_, list_, search_, update_, merge_). Descriptions are present but often generic (avg ~80 chars, below 194-char baseline). Parameter descriptions vary: some detailed, others minimal. Output schemas not documented. Error handling present but recovery guidance sparse. Missing tool annotations (readOnlyHint, destructiveHint). No idempotency guarantees stated. Composition is sound, tools are single-responsibility and chainable via IDs.
Add a comment to an existing issue
Add a comment to a pull request
Create a new branch in a GitHub repository
Create a new issue in a GitHub repository
Create or update a single file in a GitHub repository
Create a new pull request in a GitHub repository
Create a new GitHub repository in your account
Output schemas not documented. LLMs cannot infer what fields to expect from tool responses, forcing them to guess at downstream field names and risking broken tool chains.
Tool annotations missing. Destructive tools (merge_pull_request, delete operations) lack destructiveHint. Read-only tools lack readOnlyHint. This prevents agents from reasoning about safety and retry logic.
Parameter descriptions are minimal (avg ~40 chars vs 72-char baseline). Many lack context on valid ranges, formats, or dependencies. E.g., 'page' and 'per_page' lack min/max bounds; 'state' enum values not explained.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 58 | <=2025-11-25 | v2 |
Fork a GitHub repository to your account or specified organization
Get the contents of a file or directory from a GitHub repository
Get details of a specific issue in a GitHub repository.
Get details of a specific pull request
Get the review comments on a pull request
Get the list of files changed in a pull request
Get the reviews on a pull request
Get the combined status of all status checks for a pull request
Get list of commits of a branch in a GitHub repository
List issues in a GitHub repository with filtering options
List and filter repository pull requests
Merge a pull request
Push multiple files to a GitHub repository in a single commit
Search for code across GitHub repositories
Search for issues and pull requests across GitHub repositories
Search for GitHub repositories
Search for users on GitHub
Submit a formal review for a pull request with approval status and comments
Update an existing issue in a GitHub repository
Update a pull request branch with the latest changes from the base branch
No idempotency guarantees stated. Agents may retry on ambiguous failures, risking duplicate issues, PRs, or commits. Idempotent tools should declare it explicitly.
Error handling lacks recovery guidance. GitHubError classes exist but tool descriptions do not explain what to do on 404, 403, rate limit, or conflict errors. LLMs cannot self-correct.