This server has a single tool 'azmcp-extension-az' with critical definition gaps. The tool has a basic description but lacks parameter descriptions, enums, validation guidance, and output schema documentation. The input schema is minimalist (only 'command' string with no constraints, format hints, or examples). No error handling guidance is documented. The server acts primarily as a thin wrapper around the Azure CLI without proper agent-optimization patterns like parameter validation, pagination, or idempotent operation markers. Given baseline standards (94% of A+ tools have full docstrings, 100% have param descriptions), this falls well below production readiness.

• Expand tool description to 100-200 characters. Add: (1) What it does, 'Executes arbitrary Azure CLI commands and returns structured JSON output'. (2) When to use it, 'Use when the user requests Azure resource operations'. (3) Dependencies, 'Requires valid Azure CLI login and appropriate Azure permissions.' Example: 'Executes Azure CLI commands and returns structured results. Use for any Azure resource operation (create/read/update/delete). Requires valid Azure credentials. Returns JSON output or plaintext based on command result.'
• Add explicit parameter description for 'command': 'The Azure CLI command to execute (e.g., "az vm list --resource-group mygroup"). Must start with "az" or omit it. Examples: "vm list", "storage account show". Avoid combining multiple commands with semicolons, call this tool once per command.'
• Document output schema in the tool definition or server documentation. Example: '{ "type": "object", "properties": { "result": { "type": ["object", "array", "string"], "description": "Parsed JSON or plaintext from Azure CLI" }, "metadata": { "type": "object", "properties": { "original_command": { "type": "string" }, "azure_command": { "type": "string" }, "table_requested": { "type": "boolean" } } } }'
• Add error handling guidance to description: 'If the command fails, the response includes an error field. Common errors: (1) "not found", resource does not exist; verify resource-group and resource name. (2) "Insufficient permissions", user lacks required Azure role; contact administrator. (3) "Invalid syntax", command format is wrong; check Azure CLI documentation. On any error, suggest correcting the command and retrying.'

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

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