ASMP is a custom protocol framework, not a standard MCP server. Tool definitions are sparse and lack critical structure. Only 1 of 4 tools has a visible input schema (run_lint_check). Descriptions exist but are vague and lack actionable guidance. No parameter type definitions visible for most tools. No output schemas documented. Error handling is absent. The codebase shows examples in TypeScript and Python, but tool registration is incomplete and schemas are inferred rather than explicitly defined.

• Add explicit JSON Schema input definitions for all four tools. Include type, description, and constraints for every parameter. Example: validate_document should declare file_url as string with format/pattern constraints.
• Document output schemas for each tool. Specify return object structure, field types, and which fields are required for downstream tool chaining. Example: run_lint_check should document { passed: boolean, issues: number, log: string }.
• Expand tool descriptions to 100-200 characters with actionable guidance. Include WHEN to call, WHAT it returns, and any prerequisites. Example: 'Validate a document by URL or file path. Returns validation status, error message if invalid, and suggested filename. Call this before run_analysis to ensure document is readable.'
• Add error handling guidance to each tool description. Specify which errors are retryable, which require user input, and what recovery steps are available. Example: 'If validation fails due to unsupported format, try converting to PDF first.'
• Implement parameter descriptions for all inputs. For validate_document, describe file_url as 'Document URL (http/https) or local file path. Supports PDF, DOCX, TXT formats.' For risk_summary, clarify whether it requires prior state or can be called anytime.