azure-updates-mcp
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| azure_updates_searchA | Search, filter, and retrieve Azure service updates from the official JSON API. Combines keyword search, category filtering, status filtering, and date range filtering into a single flexible tool. All filter parameters are optional and can be combined. When no filters are provided, returns the most recent updates. Use this tool to:
Args: query: Optional keyword for server-side full-text search. category: Optional category to filter by (case-insensitive partial match across products, product_categories, and tags). status: Optional status filter. Valid values: Launched, In preview, In development, Retirements. start_date: Optional start date in ISO format (YYYY-MM-DD). Only include updates created on or after this date. end_date: Optional end date in ISO format (YYYY-MM-DD). Only include updates created on or before this date. Defaults to today when start_date is provided. guid: Optional unique identifier to retrieve a single specific update. When provided, all other filters are ignored and a single update is returned. limit: Maximum number of results to return (default: 10, max: 100). Set to 0 with include_facets=True for a facets-only response. Ignored when guid is provided. offset: Number of results to skip for pagination (default: 0). product: Optional product name filter (exact match against products list). product_category: Optional product category filter (exact match). include_facets: When True, includes taxonomy facets (product_categories, products, tags, statuses) with occurrence counts in the response. Use with limit=0 to get only facets (replaces category listing). Returns: Dictionary with: - total_found: Number of updates matching the filters (from API count) - updates: List of matching update objects (up to limit) - filters_applied: Summary of which filters were used - facets: (only when include_facets=True) Taxonomy with product_categories, products, tags, and statuses lists, each containing {name, count} items |
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
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clear and unambiguous.
With a single tool, naming consistency is inherently perfect. The name 'azure_updates_search' follows a clear verb_noun pattern.
The server has only one tool, which feels thin for typical server scopes. However, the tool is comprehensive and well-designed to handle all search and filter needs for Azure updates, justifying its standalone nature.
The single tool covers all necessary operations for searching Azure updates: keyword search, multiple filters, pagination, GUID retrieval, and facets. No obvious gaps exist for a read-only search domain.