A remote MCP server that uses GitHub OAuth for authentication and provides tools for GitHub API access and image generation
Three tools with mixed quality. 'add' has a trivial description (8 chars, well below 20-char minimum) and lacks parameter descriptions entirely. 'userInfoOctokit' has no description and empty schema. 'generateImage' has a reasonable description (127 chars) and well-documented parameters with constraints (min/max, enum-like descriptions). Parameter descriptions are present only for generateImage. No output schemas documented for any tool. Error handling is absent across all tools.
Add two numbers the way only MCP can
Generate an image using the `flux-1-schnell` model. Works best with 8 steps.
Get user info from GitHub, via Octokit
Two tools lack descriptions entirely ('userInfoOctokit', 'add'). LLMs cannot determine when to select these tools without explicit guidance.
'add' tool description is 8 characters ('Add two numbers the way only MCP can'), far below the 20-char minimum. Parameters 'a' and 'b' have null descriptions, violating the requirement that every parameter must have a non-empty description.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields without knowing what each tool returns.
No error handling or recovery guidance. Tools do not indicate what to do if GitHub API fails, image generation times out, or invalid parameters are passed.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 41 | 2026-07-28+ | v2 |
'userInfoOctokit' has an empty input schema ({}). While this is technically valid for a no-argument tool, the tool name does not follow verb_noun convention (should be 'get_user_info' or 'fetch_github_user').