Single tool 'certify' has a reasonable description (89 chars, within 10-1024 range) but critical schema deficiencies. Input schema lacks type declarations for parameters, 'file' and 'author_name' are both strings but have no 'type' field visible in the schema definition. No output schema is documented. The tool description does not explain what the function returns, when to use it vs alternatives, or error recovery paths. Parameter descriptions are present but minimal (file: 'Path to the file to certify', author_name: 'Optional author name'). No error handling guidance, no idempotency guarantees, no mention of prerequisites (XPROOF_API_KEY env var). The bash script implementation is visible but tool registration mechanism is not, cannot verify if this is properly registered in an MCP server wrapper.

• Add explicit JSON Schema type declarations: {"type": "object", "properties": {"file": {"type": "string", "description": "Path to file to certify (must exist and be readable)"}, "author_name": {"type": "string", "description": "Optional author name (1-255 chars)"}}, "required": ["file"]}
• Document output schema with all returned fields: proof_id (string), verify_url (string), tx_hash (string, nullable), explorer_url (string, nullable), badge_url (string). Include example response.
• Enhance tool description to 150-200 chars: 'Certify a file on MultiversX blockchain via xProof. Computes SHA-256 locally without uploading. Returns proof_id and blockchain verification URL. Requires XPROOF_API_KEY environment variable.'
• Add error handling guidance: 'On HTTP 4xx: user-fixable (invalid API key, file not found). On HTTP 5xx: retryable (service unavailable). On timeout: retryable with exponential backoff.'
• Wrap bash script in MCP server implementation (Python/Node.js/Rust) with proper tool registration, input validation (file existence, size limits), and structured JSON responses.