This server presents 5 well-documented tools with complete input schemas, clear descriptions, and proper error handling. Tool naming follows verb_noun conventions (publish_site, site_status, rollback_site, add_custom_domain, check_custom_domain). All tool descriptions are substantive and action-oriented. Input schemas use Zod with type declarations and parameter descriptions. However, output schemas are not formally documented in the code, responses are stringified JSON without an explicit response structure contract. The tool descriptions emphasize prerequisites and operational guidance (e.g., 'NEVER create a new site to update an existing one'), which is excellent for LLM reasoning. Security is well-handled: API keys are injected via environment variables (SHIPLY_API_KEY) rather than required parameters, following the secret-injection pattern. Error handling provides actionable recovery guidance ('No files to publish', 'Upload failed for X: HTTP 500'). The main gap is the absence of formal output schemas, LLMs cannot verify what fields they'll receive before calling the tools.

• Document output schemas for all tools. For example: 'Response: { slug: string; url: string; claimUrl: string; claimToken?: string; versionId: string; created: ISO8601 datetime }'. This allows LLMs to extract fields without guessing.
• Add cross-references in descriptions. Update add_custom_domain description to include 'After calling this, use check_custom_domain to poll readiness.' Similarly update check_custom_domain to reference add_custom_domain.
• Declare file/directory size limits and scalability bounds in publish_site description. E.g., 'Supports up to 10,000 files per publish; total size capped at 1 GB.'
• Add a list_publishes or get_publish_history tool to discover prior versions and claim tokens. This enables agents to retrieve, filter, and manage sites without requiring manual slug/token entry.
• Validate input in the tool implementation and return categorized errors. For example, if slug is invalid (non-alphanumeric), return 'Invalid slug format: must be 3-50 alphanumeric chars and hyphens. Got "<input>"' instead of letting the API return a 400.
• Document the relationship between claimToken (anonymous site), slug (owned site), and apiKey. Clarify that anonymous sites expire in 24h by default unless claimed; clarify that owned sites require an API key for updates.