Critical failures across all dimensions. Tool definitions are inferred from Flutter/Dart UI label files, not from actual MCP server registration code. No explicit tool schemas visible in the NestJS server source. Descriptions are present but minimal (10-30 chars, well below the 50-200 char baseline for LLM optimization). Parameters lack type definitions and constraints. No output schemas documented. Error handling and recovery guidance absent. The server appears to be a NestJS HTTP API with Flutter/Vue frontends, but the MCP tool definitions are not properly implemented in the server codebase, they exist only as UI labels in client code.

• Implement explicit MCP tool registration in Server-NestJS with full JSON Schema definitions. Move tool definitions from Flutter UI code into the server's tool registry.
• Expand all descriptions to 50-200 characters. Example: 'query_customers' → 'Search for customers by keyword, risk level, or status. Returns customer ID, name, risk level, and status. Use this to find specific customers before querying their orders or activities.'
• Add type definitions and constraints to all parameters. Use enums for status/risk_level fields. Add minLength, maxLength, pattern constraints. Document format expectations (e.g., 'ISO 8601 date').
• Document output schemas for all tools. Specify returned fields, types, pagination (limit/offset/total_count), and include IDs needed for chaining (e.g., customer_id for downstream calls).
• Add error handling guidance: 'If customer not found, try search_customers() with partial name.' Implement permission checks for destructive operations (delete_customer, update_order_amount).

Inferred effective spec: 2026-07-28+.

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