Read-only MCP validation for rights-aware production metadata manifests.
Single read-only validation tool with clear naming and basic schema. Tool name 'validate_production_manifest' correctly starts with a verb. Description is adequate (127 chars, within 10-1024 range) and explains the read-only nature. Input schema uses Zod but is overly generic (z.record(z.string(), z.unknown())), does not enforce the documented manifest structure (title, project, stage, rights_status as required strings with enums). Output schema is structured (releasable boolean + errors array) but not formally documented in the tool definition. No parameter descriptions provided. Error handling returns actionable messages ('field is required', enum violations) but lacks recovery guidance. Tool annotations correctly declare readOnlyHint=true. Missing: formal input schema matching documented constraints, parameter descriptions, output schema documentation.
Checks required project metadata, production stage, and declared rights status. Does not read files, call networks, or publish data.
Input schema does not enforce documented constraints. Schema uses z.record(z.string(), z.unknown()) instead of a strict object with required fields (title, project, stage, rights_status) and enum constraints for stage/rights_status. LLMs cannot infer valid values from the generic schema.
No parameter descriptions. The 'manifest' parameter lacks a description explaining its structure, required fields, and valid enum values. LLMs must infer from the tool description alone.
Output schema not formally documented. Tool returns {releasable, errors} but this structure is not declared in the tool definition. LLMs cannot plan downstream actions without knowing the response shape.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 52 | 2025-06-18+ | v2 |
Error messages lack recovery guidance. Errors like 'field is required' or 'rights_status=unknown is not releasable' are clear but do not suggest next steps (e.g., 'Provide a title field' or 'Use one of: cleared, licensed, synthetic').
STDIO transport only. Server is not remotely accessible and cannot be used by hosted MCP clients. Limits deployment flexibility.