This is a proxy wrapper around the GitHub MCP server that exposes 5 tools for managing toolsets and calling GitHub tools. The server has clear descriptions for most tools and reasonable parameter documentation. However, there are significant gaps: (1) Output schemas are completely undocumented, we cannot see what fields tools return, (2) The wrapper pattern introduces indirection that obscures error handling and recovery guidance, (3) Security risk: the call_github_tool tool accepts arbitrary arguments without validation or description of safety constraints. (4) The design violates single responsibility, tools like list_available_toolsets and get_toolset_tools mix discovery with recommendation. (5) Parameter descriptions lack constraints (enums, ranges, formats). Average tool score: 58/100 places this in the D-to-C range.

• Document output schemas for all tools. For example: 'Returns {"toolsets": [{"name": string, "enabled": boolean, "description": string}], "total": integer}'. Every response field must be typed and described.
• Convert 'toolset' parameter to JSON Schema enum type instead of describing valid values in text. Schema: {"type": "string", "enum": ["context", "issues", "orgs", ...]}
• Create a structured error response with error_code, error_message, and recovery_suggestion. When call_github_tool fails, return {'error': 'toolset_not_enabled', 'suggestion': 'Call enable_toolset("issues") first'} instead of raw wrapped error.
• Add per-tool risk hints (readonly/destructive/idempotent) via tool annotations in response schema. At least mark enable_toolset and call_github_tool as destructive so agents know to ask for confirmation.
• Merge list_available_toolsets and get_toolset_tools into a single 'describe_toolset(toolset_name)' that returns full details including tools within that toolset, or clearly document that list_available_toolsets must always be called first.
• Add limit and offset parameters to list_available_toolsets and list_enabled_tools. Document the default limit (e.g., 50) and that pagination is supported.
• Specify constraints on timeout_seconds: 'integer, range 1 - 300 seconds, default 30'. Document timeout behavior: 'If the tool exceeds this duration, the call returns a timeout error; the underlying operation state is unknown and may need manual cleanup.'
• For call_github_tool, document which GitHub tool names are safe to call and which require confirmation. Add guidance: 'Destructive GitHub tools (delete_repository, delete_issue) are supported but require explicit user confirmation. Check the GitHub tool's documentation before calling.'

Inferred effective spec: 2026-07-28+.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry