Argo Workflows MCP server demonstrates good definition quality with clear verb-starting tool names, comprehensive parameter schemas, and detailed descriptions. All five tools have explicit input schemas with typed parameters and descriptions. However, output schemas are not documented in the visible source code, and several tools lack error handling guidance. The tool set is well-composed for Argo-specific workflows without redundancy. Most parameters include sensible defaults and constraints (enums, ranges), though some descriptions could be more action-oriented for LLM guidance.

• Document output schemas for all five tools. Show expected response structure: field names, types, required vs optional, nested objects. Example: list_workflows returns {workflows: [{name, namespace, phase, startedAt, finishedAt, ...}], total, continue_token}.
• Add explicit error handling guidance to tool descriptions. Example for get_workflow: 'Returns 404 error if workflow not found in namespace. Try list_workflows to verify workflow name and namespace.'
• Clarify submit_workflow state-change behavior in the description. Add: 'This operation creates a new workflow and starts execution immediately. It cannot be safely retried, check if workflow already exists before retrying.'
• Document workflow_logs follow parameter behavior. Example: 'When follow=true, streams logs in real-time until workflow completes or log stream is closed. When follow=false, returns captured logs up to current time.'
• Add pagination guidance to list_workflows. Example: 'Use limit to cap results per page (default 100, max 1000). Use offset for simple pagination or continue token for resumable iteration. Do not use both offset and continue in the same call.'
• Replace submit_workflow 'parameters' free-form object with documented structure or examples. Document the expected schema: parameter names, accepted types (string, number, boolean), and validation rules. Include a note: 'Parameters depend on the workflow template, use get_workflow_template to discover available parameters first (if available).'
• Add tool annotations to the server configuration: mark read-only tools (health_check, list_workflows, get_workflow, workflow_logs) with readOnlyHint: true; mark submit_workflow with destructiveHint: true to signal irreversibility.

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

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