Skip to main content
Glama
Sign In
mcp-azure

mcp-azure

by dockndevai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List resource groups

list_resource_groups
Read-onlyIdempotent

Retrieve Azure resource groups in a subscription, filtered by an allowlist, to support governed resource inventory.

Instructions

List resource groups in a subscription (filtered by allowlist).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_resource_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
subscriptionNoSubscription id (defaults to AZURE_SUBSCRIPTION_ID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.2
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.1.1

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint, so the safety/behavior profile is well covered. The description adds an unexplained 'allowlist' filter constraint but doesn't say who controls it, whether access failures are surfaced, or how results are ordered or paginated.

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?

A single short sentence, front-loaded with the action. The parenthetical is terse to the point of being unclear, but there is no waste.

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

Completeness3/5

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

For a zero-required-param list tool with rich annotations and full schema coverage, the core need is met. However, the unexplained allowlist filtering leaves an agent unsure whether calls will silently return empty or fail, which is meaningful context for a discovery tool.

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

Parameters3/5

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

Schema coverage is 100% and the single parameter 'subscription' is fully documented in the schema including its AZURE_SUBSCRIPTION_ID default. The description adds nothing beyond the schema, so baseline 3 applies.

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

Purpose4/5

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

Clear verb+resource ('List resource groups') with a scope qualifier ('in a subscription'). It's distinguishable from siblings like list_subscriptions and list_resources, though the parentheses note about allowlist filtering is cryptic and unexplained.

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

Usage Guidelines3/5

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

The phrase 'filtered by allowlist' implies a usage constraint but never states when to use this versus list_resources, whether the allowlist is user-configurable, or what happens when a subscription isn't in the allowlist. No explicit when/when-not guidance or alternatives named.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools