Skip to main content
Glama
Sign In
Stratos

Stratos

by h4cd0c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

azure_enumerate_resource_groups

Enumerate all Azure resource groups in a subscription, returning names, locations, IDs, and tags. Optionally filter by location.

Instructions

Enumerate all resource groups in a specific subscription. Returns name, location, ID, and tags. Supports location filtering.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "subscriptionId": "<subscriptionId>"
    },
    "name": "azure_enumerate_resource_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
subscriptionIdYesAzure subscription ID (format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)
locationNoFilter by location(s): single (e.g., 'eastus'), multiple (e.g., 'eastus,westeurope'), or preset ('common', 'all')
formatNoOutput format: 'markdown' (default, human-readable) or 'json' (machine-readable)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.0

TDQS

B3.4/5.0
Behavior2/5

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

Annotations are empty, so the description must fully disclose behavior. It states it enumerates resource groups and returns specific fields, but does not mention whether the operation is read-only, any required permissions, error handling for invalid subscription IDs, or rate limits. The description is thin on behavioral context.

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

Conciseness5/5

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

Two concise sentences cover the purpose, return fields, and filtering capability. No unnecessary words; each sentence earns its place.

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

Completeness4/5

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

Given the lack of output schema, the description compensates by listing return fields. It covers the main functionality and the three parameters are fully described in the schema. Missing some behavioral context (permissions, errors) but for a simple enumeration tool, it is fairly complete.

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%, so the baseline is 3. The description adds some value by mentioning that the output includes name, location, ID, and tags, and that location filtering is supported, but the filtering details are already in the parameter descriptions. The added output information is not overwhelming.

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 the verb 'Enumerate', the resource 'resource groups', and the scope 'in a specific subscription'. It also lists what is returned (name, location, ID, tags) and indicates location filtering. This differentiates it from sibling enumeration tools like azure_enumerate_managed_identities.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, use cases, or situations where another tool would be more appropriate given the many sibling enumeration tools.

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