A Model Context Protocol server for creating GitHub repositories
Single tool with basic schema and minimal descriptions. Tool name 'create_repository' follows verb_noun convention (+), but description is generic (18 chars, below 20-char threshold). Input schema present with type and required fields, but parameter description is minimal (29 chars). No output schema documented. Error handling exists but lacks recovery guidance. No parameter constraints (enums, ranges). Tool is write-heavy (WRITE risk) with no confirmation/dry-run pattern. Overall: functional but well below production baseline (194 chars avg description, 72 chars avg param annotation).
Creates a new repository on GitHub
Tool description is 18 characters ('Creates a new repository on GitHub'), below 20-char minimum. Lacks WHEN to use, prerequisites, or state-change clarity. LLMs cannot reliably select this tool when similar tools exist.
Parameter 'repository_name' description is 29 characters ('The name of the repository to create'). Missing format constraints (allowed characters, length limits, naming rules). LLMs will pass invalid names without guidance.
No output schema documented. Tool returns text response with Japanese error messages, but LLMs cannot parse structured fields (repo_url, repo_id, owner) for downstream chaining. Breaks tool composition.
Destructive write operation (creates GitHub repository) lacks confirmation/dry-run pattern. No idempotent hint. Agents cannot safely retry on ambiguous failures without risking duplicate repositories.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 40 | 2026-07-28+ | v2 |
Error messages are in Japanese ('リポジトリの作成に失敗しました') and lack recovery guidance. LLMs cannot parse non-English errors or determine if failure is retryable, user-fixable, or fatal.