MCP server for managing users and groups, providing tools to add users to groups, retrieve user data by email, and list available groups
Server has 3 tools with basic descriptions but critical gaps in schema completeness, parameter documentation, and error handling. Tool names lack clear verb-noun structure (AddUser vs add_user). Input schemas present but parameters lack descriptions, AddUser's 'userToAddToGroup' object has no field-level schema. GetUsers and GetGroups descriptions are minimal (10-30 chars, below 34-char p10 baseline). No output schemas documented. No error handling guidance, validation rules, or recovery paths. No tool annotations (readOnlyHint/destructiveHint). Composition is reasonable (3 single-purpose tools) but parameter naming is inconsistent with agent conventions.
Add user to group
Get groups data
Get user data based on their email
AddUser input schema incomplete: 'userToAddToGroup' is typed as object with description 'User data' but no nested field schema (userId, groupId, etc.). LLM cannot infer required fields or their types.
Tool descriptions too short (10-30 chars vs 34-char baseline p10). 'Get user data based on their email' and 'Get groups data' lack context on when to use, what structure is returned, or dependencies. LLMs cannot reliably select these tools.
No output schemas documented. GetUsers returns User? and GetGroups returns List<Group>? but LLM has no visibility into field names, types, or structure. Breaks downstream tool chaining.
No error handling or recovery guidance. HTTP failures (404, 500, timeout) return raw status codes. LLM cannot determine if error is retryable, user-fixable, or fatal.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 33 | 2026-07-28+ | v2 |
Tool names use PascalCase (AddUser, GetUsers, GetGroups) instead of snake_case verb_noun convention (add_user, get_users, get_groups). Inconsistent with agent tool naming baselines and harder for LLMs to parse intent.