Skip to main content
Glama

azure_check_cli

Verify Azure CLI installation and authentication status to ensure proper configuration for Azure DevOps workflows and container deployments.

Instructions

Check Azure CLI installation and authentication

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that implements the azure_check_cli tool. It performs checks for Azure CLI installation and login status using the commandRunner utility.
    export async function azureCheckCli() {
      const checks = [];
    
      const azVersion = await commandRunner("az --version | head -1");
      if (azVersion.success) {
        checks.push(`[OK] Azure CLI: ${azVersion.stdout}`);
      } else {
        checks.push(`[FAIL] Azure CLI not installed\n       Install from: https://docs.microsoft.com/cli/azure/install-azure-cli`);
        return { content: [{ type: "text", text: checks.join("\n\n") }] };
      }
    
      const account = await commandRunner("az account show --query '{name:name, id:id}' -o tsv");
      if (account.success) {
        checks.push(`[OK] Logged in to Azure\n       Account: ${account.stdout.split("\t")[0]}`);
      } else {
        checks.push(`[FAIL] Not logged in to Azure\n       Run: az login`);
      }
    
      return { content: [{ type: "text", text: checks.join("\n\n") }] };
    }
  • src/tools.js:576-597 (registration)
    The tools object exports all available tools, including azureCheckCli, which registers it for the MCP server.
    export const tools = {
      // Git
      gitStatusExplained,
      gitBranchExplained,
      gitCommitGuided,
      // Docker
      dockerCheckSetup,
      dockerAnalyzeProject,
      dockerBuild,
      // GitHub
      githubSecretsList,
      githubSecretsSet,
      // Azure
      azureCheckCli,
      azureAcrSetup,
      azureContainerAppsDeploy,
      // SonarCloud
      sonarcloudSetupGuide,
      sonarcloudCreateConfig,
      // Onboarding
      devOnboardingCheck,
    };
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does but doesn't reveal critical traits like whether it performs read-only checks, requires specific permissions, outputs diagnostic details, or has side effects (e.g., modifying configurations). This leaves significant gaps for an agent to understand the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core purpose without any wasted words. It's appropriately sized for a simple tool with no parameters, making it easy to parse and understand quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate but lacks completeness. It doesn't explain what the check entails, what outputs or errors to expect, or how it integrates with sibling Azure tools, leaving the agent with incomplete context for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description appropriately doesn't add parameter details, aligning with the baseline score for parameterless tools, though it could mention if any implicit inputs (like environment variables) are used.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with specific verbs ('check') and resources ('Azure CLI installation and authentication'), making it immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'dev_onboarding_check' or 'docker_check_setup', which might have overlapping diagnostic functions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, such as other Azure setup tools or general diagnostic siblings. It lacks explicit context, prerequisites, or exclusions, leaving usage decisions to inference based on the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rideRTD/RTD-DevOps'

If you have feedback or need assistance with the MCP directory API, please join our Discord server