Critical failures across all dimensions. No tool schemas visible in source code, cannot verify input parameter types, constraints, or output structures. Tool descriptions are inferred from names only; no actual descriptions found in the provided code. The server.js and package.json show a Next.js + Prisma CRM application, but the actual MCP tool definitions in src/mcp/tools/*.ts are not included in the source excerpt. Without access to the tool registration code, all schema and description scores default to 0. This is a hard cap per the rubric: 'If you cannot see the actual tool definition in the source (only inferred): cap that tool's overall at 50.' Since NO tool definitions are visible, the entire definition quality score collapses.

• Provide the actual tool definition files (src/mcp/tools/admin.ts, billing.ts, calendar.ts, forms.ts, leads.ts, mail.ts, outreach.ts) so schemas and descriptions can be verified.
• Add comprehensive descriptions (50 - 200 characters) to every tool explaining WHAT it does, WHEN to use it, and what it returns. Example: 'Create a new user account with email and role. Returns user_id for use in subsequent calls.'
• Add type-annotated input schemas with descriptions for every parameter. Example: { user_email: { type: 'string', description: 'Email address (required for login)' }, role: { type: 'string', enum: ['admin', 'user', 'viewer'], description: 'User role (default: user)' } }
• For list tools, add pagination parameters (limit: 1 - 100, default 20; offset or cursor) and return total_count or next_cursor in responses to prevent context window exhaustion.
• For destructive tools (delete_*, cancel_*), implement a confirmation pattern: add a 'confirm' boolean parameter (default false) that returns a summary without executing, or add a separate 'confirm_delete_*' tool that requires explicit confirmation.

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

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