Single tool 'github_me' with minimal definition. Tool has a clear verb-noun name and basic description, but parameter annotations are completely absent. Input schema is present but empty (no parameters to describe). No output schema documented. No error handling guidance. This is a barebones implementation that does not follow LLM-optimized tool definition patterns.

• Expand tool description from 50 to 150-200 characters: 'Fetch the authenticated GitHub user's profile information (name, login, email, bio, public repos, followers, etc.). Requires prior GitHub OAuth authentication. Returns structured profile data or error if user not found or API request fails.'
• Add explicit output schema to ListToolsRequestSchema response documenting return fields: {type: 'object', properties: {name, username, email, bio, public_repos, followers, following, created_at, updated_at, profile_url}, required: [username, profile_url]}
• Document error cases in tool description: 'Returns error with status code and message if GitHub API fails (401 Unauthenticated, 403 Forbidden, 500 Server Error). Suggest user re-authenticate if token is expired.'
• Add tool annotation hints to capabilities: {readOnlyHint: true, idempotentHint: true} to signal to LLM that this tool is safe to call repeatedly without side effects
• Include OAuth prerequisite in description: 'Note: This tool requires the user to have completed GitHub OAuth flow first. If not authenticated, authentication will fail.'
• Return structured JSON response instead of formatted text. Replace multiline string with {type: 'object', properties: {name, login, email, bio, public_repos, followers, following, created_at, updated_at, html_url}} and include all fields in response for downstream tool chains

Inferred effective spec: <=2025-11-25.

• Relies on Stateful initialize / Mcp-Session-Id (removed; protocol is stateless) - make each request self-contained