linky-mcp provides three Linkerd-focused tools with clear verb-based naming (list, get, apply) and documented input schemas. However, critical gaps exist: output schemas are completely undocumented, descriptions lack LLM-optimization guidance, parameter descriptions are minimal, and error handling strategies are absent. The destructive 'install_apply' tool lacks confirmation/dry-run safeguards typical of production tools. Tool definitions are explicit in the source code (pkg/toolsets/linkerd/), so no inference penalty applies, but the implementation falls short of production-grade standards. Average per-tool score: 62 across naming (78), description (48), and schema (58).

• Document output schemas for all three tools. For list: return array of {name, namespace, status, labels, ports, created_at}. For get: return full server manifest with metadata, spec, and status. For apply: return {status: 'success'|'error', applied_resources: string[], warnings: string[]}.
• Split install_apply into install_preview (dry-run, returns planned changes) and install_apply (requires explicit profile+confirm, returns result). Add per pattern:confirmation-request.
• Add enum constraints to profile parameter: profile: enum('default'|'minimal'|'high-availability'|'ha-mtls'). Document valid values in parameter description.
• Document range and defaults for numeric/pagination params. E.g., 'limit: Maximum number of servers (1-100, default 20)'; 'continue: Pagination token from previous response (optional)'.
• Add error handling guidance to descriptions. E.g., for get_server: 'Returns error if server not found. Try list_servers to verify name and namespace.'
• Clarify idempotency: 'Calling install_apply twice with same profile is safe (idempotent). Changing profile and re-applying may trigger updates.'
• For list_servers, document filtering behavior: 'If namespace omitted, lists servers across all namespaces. labelSelector uses Kubernetes label query syntax.'
• Add dependency hints: 'Call policy_servers_list first to discover available servers and their namespaces before calling policy_server_get.'

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

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