The k8m MCP server exposes only one tool: 'save_k8s_yaml_template'. Critical issues: (1) Tool name lacks action clarity, 'save' is weak and could be confused with 'store' or 'persist'; 'save_k8s_yaml_template' is 28 characters but does not follow verb_noun convention cleanly. (2) Description is in Chinese ('保存Yaml为模版' = 'Save YAML as template'), not English, LLMs expect English documentation for proper understanding. (3) Parameters have descriptions in Chinese ('模板适配集群（可为空）' = 'template-adapted cluster (optional)'), again creating a language barrier. (4) Schema is partially visible but underdocumented: 'cluster' param has description but 'required' status is not explicit; 'yaml' is marked required but no format/length constraints documented; 'name' lacks a clear description of what constitutes a valid template name (length, chars, uniqueness?). (5) No output schema documented, what does the tool return on success? What fields? What error states? (6) No error handling guidance visible, if the YAML is malformed, if the template name already exists, or if the cluster is invalid, how does the tool respond and what should the LLM do next? (7) Input validation rules not stated, no regex pattern for 'name', no size limit for 'yaml' content. (8) The tool is marked WRITE risk, which is good, but the description does not state 'This tool creates/persists a template' explicitly, LLMs need to know if this is idempotent or if repeated calls with the same name overwrite.

• Translate all tool and parameter descriptions to English. Example: 'Save a Kubernetes YAML configuration as a reusable template. Templates can be filtered by cluster and retrieved by name for later instantiation.'
• Document the full output schema: What fields does the response include? Example: { 'template_id': string, 'name': string, 'created_at': ISO8601, 'cluster': string | null, 'yaml_size_bytes': number }
• Add comprehensive parameter validation rules. Example for 'name': 'Template name (1-255 alphanumeric + underscore/hyphen, must be unique within cluster scope)'. For 'yaml': 'YAML content as text (max 100KB, must be valid YAML syntax)'. For 'cluster': 'Optional cluster name (alphanumeric + hyphen, empty string means apply to all clusters)'.
• Document error cases and recovery guidance: 'If YAML parsing fails, return error code INVALID_YAML with the line number and offending text. If template name already exists, return DUPLICATE_NAME and suggest alternatives. If cluster is unknown, return UNKNOWN_CLUSTER and list available clusters.'
• Clarify idempotency: 'Saving a template with an existing name overwrites the previous version. This operation is idempotent: repeated calls with identical input produce identical results.'
• Consider renaming to 'create_k8s_yaml_template' or 'store_k8s_yaml_template' for clearer intent, and update the description to explicitly state: 'Creates or updates a YAML template' and 'This is a stateful write operation; repeated calls overwrite the template.'

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

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