StealthSurf MCP server demonstrates solid foundational quality with consistent naming patterns, documented descriptions, and structured schemas across all 6 tools. Tool names follow verb_noun convention (cloud_servers_list, cloud_servers_get_stats, cloud_servers_reboot, etc.), aligning well with agent expectations. All tools have substantive descriptions (100-200 chars range, exceeding the baseline average of 194 chars). Input schemas are present and typed using Zod with parameter descriptions. However, there are notable gaps: output schemas are not documented anywhere in the code (critical for agentic composition), error handling lacks guidance for recovery, tool annotations (readOnlyHint/destructiveHint/idempotentHint) are applied but not consistently used across all tools, and some parameters have loose constraints (e.g., 'promocode' accepts 4-32 chars but no validation pattern is visible). The codebase shows evidence of thoughtful design (e.g., the setup-cloud-server prompt demonstrates multi-step orchestration), but production-grade agentic tooling requires explicit output documentation and more granular error handling.

• Document output schemas for all 6 tools. Create a schema object or JSDoc comment detailing fields, types, and example values. E.g., cloud_servers_list returns [{id: number, location_id: number, status: 'ordered'|'active', expires_at: string (ISO 8601), url: string, is_online: boolean, auto_renewal: boolean, hostname: string}].
• Enhance error messages with recovery guidance. Wrap API errors and categorize them: 'Server not found (404, retryable). Try cloud_servers_list to verify the ID.' or 'Insufficient balance (402, user-fixable). Add funds via add_balance before retrying.' Implement using a standardized error response object.
• Add minLength, maxLength, and pattern constraints to Zod schemas. E.g., z.string().min(4).max(32) for promocode, z.string().max(255) for hostname. Zod validates server-side; the constraint also appears in the schema and helps LLMs avoid invalid input.
• Implement a dry-run mode for irreversible tools. Add an optional 'dry_run: boolean' parameter to cloud_servers_create_order and cloud_servers_renew. When true, return estimated costs and requirements without creating the order. This allows agents to preview before committing.
• Make tool annotations explicit and consistent. Ensure cloud_servers_reboot has a destructiveHint annotation (even though it's reversible, it disrupts the server). Add explicit writeHint/idempotentHint to all mutating tools. Export a consistent annotations object and apply it uniformly.
• Document conditional parameter logic formally. For cloud_servers_toggle_auto_renewal, restructure as: if enabled=true, days is required; if enabled=false, days is optional/ignored. Consider splitting into separate tools (enable_auto_renewal with days, disable_auto_renewal with no params) to eliminate the conditional.