OxiDex MCP has 9 tools with reasonable naming (verb_noun pattern) and basic schemas, but critical gaps undermine quality. Tool descriptions are present but generic (avg ~80 chars, below 194-char baseline). Parameter descriptions are sparse or missing entirely, most params lack actionable guidance on format, constraints, or valid values. Output schemas are completely undocumented; LLMs cannot predict response structure. Error handling is absent, no recovery guidance, no categorization, no actionable messages. The server is STDIO-only, capping protocol readiness at 50. Overall, this is a D-grade server with functional definitions but insufficient LLM-optimization and missing production patterns.

• Document output schemas for all 9 tools. Example: extract_metadata should return {files: [{path: string, metadata: {[key: string]: string}}], errors: [{path: string, reason: string}]}. This enables LLMs to chain tools and extract the right fields.
• Expand parameter descriptions with format and constraint guidance. E.g., 'filters' in search_metadata: 'Array of filter expressions in format KEY=VALUE or KEY>VALUE (e.g., ["Make=Canon", "DateTimeOriginal>2024-01-01"]). Supported keys: Make, Model, DateTimeOriginal, etc.'
• Add error handling with recovery hints. E.g., 'If path not found, try search_metadata() to locate files. If glob pattern matches 0 files, check syntax (e.g., *.jpg not *.JPG).'
• Enhance tool descriptions to 150-250 chars, clarifying WHEN to use each tool. E.g., extract_metadata: 'Extract EXIF and metadata tags from image files. Use this to inspect raw metadata; use analyze_metadata for statistical summaries. Supports glob patterns for batch operations.'
• Add explicit dry-run confirmation for write_metadata and copy_metadata. Update descriptions: 'Modifies metadata on disk. Set dry_run=true to preview changes before applying. Supports glob patterns for batch updates.'

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

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