mcp-azure
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_subscriptionsA | List subscriptions the service principal can see (filtered by allowlist). |
| list_locationsA | List the regions available to a subscription. |
| list_resource_groupsA | List resource groups in a subscription (filtered by allowlist). |
| list_resourcesA | List resources in a subscription, or within a specific resource group. |
| get_resourceA | Fetch a resource by its full ARM id. Provide the api-version for the resource type. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct level of the Azure hierarchy: subscriptions, locations, resource groups, resource collection, and individual resources by ARM ID. There is no overlap between them, and list_resources clearly differs from get_resource by operating on collections rather than a single resource.
All tools follow a consistent snake_case verb_noun pattern: list_* for collection operations and get_ for a single resource fetch. The naming is predictable and uniform across the entire set.
Five tools is well-scoped for a read-only Azure resource explorer. Each tool covers a meaningful and distinct part of the subscription/resource group/resource hierarchy without unnecessary duplication or bloat.
The tool set provides solid coverage for read-only Azure inventory: subscriptions, regions, resource groups, resource listing, and individual resource retrieval. Minor gaps exist such as no direct get for a subscription or resource group by name, and no write/management operations, but that appears to align with the apparent read-only purpose.