feathers-mcp defines 4 tools with basic schemas and descriptions. However, the server has significant gaps in parameter documentation, output schema specification, error handling guidance, and tool composition. Tool names lack action verbs (whoami, hidden_tool, boom, echo_json are not verb_noun patterns). Descriptions are minimal (under 100 chars each) and lack context for when/why to use each tool. Input schemas are present but parameters lack descriptions. Output schemas are not documented. The test tools appear minimal/incomplete for a production framework. Code shows proper TypeScript typings and Zod integration, but MCP-specific quality patterns are underutilized. Average tool score: 52 across 4 tools.

• Rename tools to follow verb_noun pattern: 'whoami' → 'get_current_user', 'echo_json' → 'echo_structured_data', 'boom' → 'test_error_handling'. Action verbs at the start make intent clear to LLMs.
• Add detailed parameter descriptions. For whoami's 'delayMs': 'Milliseconds to delay response (0-5000). Used for testing concurrent request handling.' For echo_json's 'value': 'String value to echo back as JSON. Max 10000 characters.'
• Document output schemas for each tool. Add to class definitions or descriptions: 'Returns: {email: string, userId: number}' for whoami; 'Returns: {value: string, timestamp: ISO8601}' for echo_json.
• Enhance tool descriptions (10-200 chars). Example: whoami: 'Get the email address of the currently authenticated user. Required for multi-tenant operations. Returns 401 if unauthenticated.' boom: 'Test error handling in MCP clients. Always throws a fatal error. Use to verify error recovery in agents.'
• Add error handling guidance. For whoami: 'Throws 401 if not authenticated, ensure agent has valid credentials. Throws 403 if multi-tenant context missing, provide tenant_id parameter.' For boom: 'Always throws, this is intentional for testing client error paths.'
• Mark hidden_tool as private/internal or remove it. If it must exist, add schema annotation (toolAnnotations) with readOnlyHint or document why it appears in the schema.
• Consider whether echo_json is a production tool or test fixture. If test-only, move it to a separate test server. If production, clarify its use case and add validation for input size/format.

Inferred effective spec: 2026-07-28+.

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