Feed Formulation Backend - MCP Server Fork. A simplified dairy cattle nutrition optimization system optimized for MCP server integration with multi-tenant support.
Critical gaps across all dimensions. Tool descriptions are present but generic (avg ~60 chars, below 194-char baseline). Input schemas visible but severely underdeveloped: most parameters lack type constraints, enums, or validation guidance. No output schemas documented. Parameters like 'action' (tools 6-9) are free-form strings inviting hallucination. Authentication tools expose sensitive operations (PIN, OTP, passwords) without confirmation patterns or dry-run support. Admin/superadmin tools lack permission gates, audit trails, or scope declarations. No error handling guidance visible. Composition issues: manage_feeds_admin, manage_country_admin, manage_multi_tenant, and manage_superadmin all use generic 'action' + 'data' patterns, forcing LLMs to guess valid action values. Tool names lack clarity: 'manage_*' is vague; 'create_feed', 'update_feed', 'delete_feed' would be clearer. No evidence of idempotency, rate limiting, or secret injection patterns.
Traditional email + PIN authentication (backward compatible)
OTP (One-Time Password) authentication
Diet formulation and evaluation for dairy cattle nutrition optimization
Public feeds endpoints - retrieve feed data by ID or search
Country-level admin endpoints for regional management
Minimal admin functions for feed management and data import
Multi-tenant management - Organization and API key management
Superadmin management endpoints for system-wide administration
Generic 'action' parameter with no enum constraint or documentation. Tools 6-9 (manage_feeds_admin, manage_country_admin, manage_multi_tenant, manage_superadmin) accept free-form action strings ('create', 'update', 'delete', 'import') with no validation guidance. LLMs cannot discover valid actions and will hallucinate invalid values.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., feed_id, organization_id). Violates pattern:tool and mxe:include-chaining-ids.
Authentication tools (authenticate_email_pin, authenticate_otp, register_organization) lack confirmation/dry-run patterns and do not declare WRITE risk in descriptions. No guidance on irreversible consequences or recovery steps.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 37 | <=2025-11-25 | v2 |
Organization registration and login
Admin/superadmin tools (manage_feeds_admin, manage_country_admin, manage_multi_tenant, manage_superadmin) lack permission gates, scope declarations, and audit trail guidance. No evidence of least-privilege enforcement or role-based access control.
Parameter descriptions are generic or missing validation rules. 'feed_id' (tool 1) lacks format guidance. 'requirements' (tool 2) is an object with no schema. 'action' parameters (tools 6-9) have no enum or valid value list. Violates pattern:tool-description and review:param-validation-rules.