Skip to main content
Glama
jonnybottles

azure-updates-mcp

by jonnybottles

azure_updates_search

Search and filter Azure service updates by keyword, category, status, and date range to find relevant platform changes.

Instructions

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:

  • Browse recent updates (no filters)

  • Search for updates mentioning a specific topic (query="AKS")

  • Filter by product (product="Azure Kubernetes Service")

  • Filter by product category (product_category="Compute")

  • Filter by service category (category="Azure Kubernetes Service") -- partial match across all taxonomy

  • Find updates by status (status="In preview", "Launched", "Retirements", "In development")

  • Get updates in a date range (start_date="2025-01-01", end_date="2025-01-31")

  • Retrieve a specific update by its GUID/ID (guid="...")

  • Combine any of the above (query="networking" + status="Launched")

  • Paginate with offset (offset=10, limit=10 for page 2)

  • Discover available categories and taxonomy (include_facets=True, limit=0)

  • Get an overview with facets + recent items (include_facets=True, limit=10)

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNo
categoryNo
statusNo
start_dateNo
end_dateNo
guidNo
limitNo
offsetNo
productNo
product_categoryNo
include_facetsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It explains that all filters are optional, default returns recent updates, guid overrides other filters, and facets behavior. It also mentions the return structure. There is no contradiction.

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

Conciseness4/5

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

The description is well-structured with a clear opening, a bulleted use-case list, and parameter explanations. It is thorough but slightly lengthy; however, every sentence adds value. It front-loads the core purpose before detailing options.

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

Completeness5/5

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

Given 11 parameters and an output schema, the description explains all parameter interactions, pagination, facets, and return dictionary fields. It is complete enough for an agent to use the tool correctly without additional context.

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

Parameters5/5

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

The schema has 0% description coverage, so the description must fully explain each parameter. It does so comprehensively: all 11 parameters are described with types, defaults, allowed values (e.g., status enum), and behaviors (e.g., limit=0 for facets-only). This adds significant meaning beyond the schema.

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

Purpose5/5

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

The description clearly states that the tool searches, filters, and retrieves Azure service updates from the official JSON API. It emphasizes combining multiple filter types into one flexible tool, which distinguishes it from potential siblings (though none listed).

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

Usage Guidelines4/5

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

The description provides a detailed bulleted list of use cases, from browsing recent updates to filtering by various criteria and using facets. It explains when to use each parameter combination, including the behavior when guid is provided. However, it does not explicitly mention when not to use the tool or suggest alternatives.

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/jonnybottles/azure-updates-mcp'

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