MCP server for monitoring data pipeline health, detecting schema drift, and identifying anomalies in agentic data pipelines
Critical failures across all dimensions. Tool definitions are minimal and lack essential structure. execute_skill_action has no visible input schema or parameter descriptions. inspect_data_pipeline has a schema but descriptions are generic and under 20 chars. No error handling guidance, no output schema documentation, no security considerations. Tool names lack clarity (execute_skill_action is vague; inspect_data_pipeline is acceptable). The server appears to be a stub implementation with hardcoded mock responses rather than a production-ready MCP server.
Execute skill action for data pipeline observability and schema drift monitoring
Inspect a data pipeline for anomalies, schema drift, null rate spikes, and health status
execute_skill_action has no input schema visible in source code. Tool definition is incomplete and cannot be validated by LLMs.
Tool descriptions are too short and lack actionable context. execute_skill_action description (58 chars) does not explain what 'skill action' means or when to use it. inspect_data_pipeline description (113 chars) is generic.
No output schema documented for either tool. LLMs cannot plan downstream calls or extract required fields. inspect_data_pipeline returns hardcoded mock data with no schema specification.
No error handling or recovery guidance. Tools return mock data only; no error cases, validation, or actionable error messages defined.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 28 | 2026-07-28+ | v2 |
Parameter descriptions missing for inspect_data_pipeline inputs. 'pipeline_name' and 'table_target' have no descriptions explaining format, constraints, or valid values.