Azure Impact Reporting 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| report_impact_to_azureB | Reports the impact to Azure. Typically called when customers facing issue with azure infrastructure and they want to let azure know about it. Args: subscriptionid (str): The Azure subscription ID where the resource is present. Eg: 68fa15fd-eef2-4ca3-a053-bcf268bd7371 resourcegroup (str): The Azure resource group name where the resource is present. Eg: test-rg resourceprovider (str): The Azure resource provider name for the resource. Eg: Microsoft.Compute resourcetype (str): The Azure resource type. Eg: virtualMachines resourcename (str): The Azure resource name. Eg: test-vm impactcategory (str): The impact category denoting the underlying issue. Can be one of: Resource.Connectivity, Resource.Performance, Resource.Availability or Resource.Unknown if the issue is not known. |
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 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The single tool has a clear, distinct purpose: reporting impact to Azure for infrastructure issues.
The single tool name follows a clear verb_noun pattern (report_impact_to_azure). Since there is only one tool, consistency is inherently perfect with no deviations to assess.
One tool is too few for a server named 'Azure Impact Reporting MCP Server', which suggests a broader scope for impact reporting in Azure. A single tool feels thin and incomplete for handling various aspects of impact reporting, such as querying, updating, or managing reports.
The tool surface is severely incomplete for impact reporting. It only allows reporting impact but lacks essential operations like retrieving existing reports, updating reports, deleting reports, or listing reports, which are necessary for a full lifecycle of impact management in Azure.