Multi-server MCP agent system with GitHub, Project Management, and Calendar servers providing tools for enterprise operations
Critical gaps across all dimensions. Tool definitions are inferred from file paths and brief descriptions only, no visible input schemas, parameter types, or output documentation in provided source. Descriptions are minimal (10-50 chars), far below the 194-char baseline for production tools. No evidence of parameter validation, error handling guidance, or security controls. The sample code shows tool execution infrastructure but not the actual tool definitions themselves. This server cannot be reliably used by LLMs without complete schema and description overhauls.
Create a new pull request on GitHub
Create a new ticket in project management system
Retrieve calendar availability and free time slots
Retrieve backlog items from project management system
Retrieve CI/CD pipeline status from GitHub
Retrieve commits from GitHub repository
Retrieve issues from GitHub repository
Retrieve calendar meetings and events
Retrieve calendar notes and meeting notes
No input schemas visible for any tool. Cannot verify parameter types, constraints, or required fields.
Descriptions are 10 - 50 characters, far below the 194-char production baseline. Examples: 'Retrieve pull requests from GitHub repository' (47 chars) lacks WHEN to use, prerequisites, or what fields are returned.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 30 | 2026-07-28+ | v2 |
Retrieve pull requests from GitHub repository
Retrieve sprint information from project management system
Retrieve tickets from project management system
Retrieve team velocity metrics from project management system
Merge a pull request on GitHub
Move a ticket to a different sprint
Update an existing GitHub issue
Update an existing ticket in project management system
No parameter descriptions visible. LLMs cannot infer what 'status', 'filter', 'limit', or 'offset' mean without explicit descriptions.
Write operations (create_pull_request, update_issue, merge_pull_request, create_ticket, update_ticket, move_ticket_to_sprint) lack confirmation/dry-run patterns and error recovery guidance. No evidence of idempotency or rollback support.
No output schemas documented. LLMs cannot plan downstream tool calls or extract required fields (e.g., PR ID for merge, ticket ID for update). Pagination support (limit, offset, total_count) not visible.