avm-mcp-server
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_avm_modulesA | List Azure Verified Modules (AVM). If modulename is provided, return details for that specific module. Args: modulename (str): AVM Module name to filter by Returns: str: a list of AVM modules in JSON format with their versions and documentation links |
| scrape_avm_module_detailsA | Fetch and extract specific sections from AVM module README.md, returning formatted markdown. Extracts:
Converts GitHub URLs like: https://github.com/Azure/bicep-registry-modules/tree/main/avm/res/storage/storage-account To raw URLs like: https://raw.githubusercontent.com/Azure/bicep-registry-modules/refs/heads/main/avm/res/storage/storage-account/README.md Args: url (str): AVM GitHub repository URL Returns: str: Formatted markdown string containing the extracted sections |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| find_avm_module_prompt | A prompt to find Azure Verified Modules (AVM). |
| get_avm_module_details_prompt | A prompt to get the details of a specific AVM. |
| suggest_avm_for_service_prompt | A prompt to suggest an AVM for a specific Azure service. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
list_avm_modules and scrape_avm_module_details have clearly distinct purposes: one lists modules with metadata, the other extracts detailed sections from a module's README. No overlap.
Both tool names follow a consistent verb_noun pattern with snake_case: list_avm_modules and scrape_avm_module_details. The naming is predictable and clear.
With only two tools, the surface feels thin for a server dedicated to Azure Verified Modules. While the tools are useful, the count is borderline minimal for a full-featured interaction.
The two tools cover listing modules and extracting detailed documentation, which are the core read operations. Minor gaps exist (e.g., no search by resource type) but agents can work around them.