Opsphere — DevOps & SRE Intelligence

Azure CLI — Generic Read-Only Query

azure_cli_query

Read-only

Executes any read-only Azure CLI command (az …). Only allows read-only verbs: list, show, get, describe, check, verify, query, search, count, export. Never allows write, delete or secret-value operations. Examples: "network dns zone list", "servicebus namespace list --resource-group my-rg", "vm list", "storage account list", "monitor metrics list --resource /subscriptions/…".

Input Schema

Name	Required	Description
`command`	Yes	Azure CLI command WITHOUT the leading "az" prefix. Example: "network vnet list" or "servicebus namespace list --resource-group my-rg"
`context_id`	No	Optional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.
`azure_tenant_id`	No	Azure tenant ID (optional — defaults to AZURE_TENANT_ID from tenant config)

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	Yes
`contractVersion`	Yes
`dataSchemaVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 26, 2026

changedOutput schema / properties / data / properties / parsedJson / additionalProperties
```
Previous value: -trueNew value: +false
```
addedOutput schema / properties / data / properties / parsedJson / properties / count
```
Added value: +{
+  "type": "number"
+}
```

addedOutput schema / properties / data / properties / parsedJson / properties / items

Added value: +{
+  "items": {
+    "additionalProperties": {
+      "type": [
+        "string",
+        "number",
+        "boolean",
+        "null"
+      ]
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / dataSchemaVersion

Added value: +{
+  "const": 1,
+  "type": "number"
+}

changedOutput schema / required

Previous value: -[
-  "contractVersion",
-  "ok",
-  "data"
-]New value: +[
+  "contractVersion",
+  "dataSchemaVersion",
+  "ok",
+  "data"
+]

First observedOct 15, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/destructiveHint=false, but the description adds substantive behavior: an explicit allowlist of read verbs and an explicit exclusion of secret-value reads, which the annotations do not convey. It stops short of mentioning permission prerequisites, throttling, or how command failures surface.

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?

Three tight sentences: capability first, constraint second, concrete examples last. No redundancy or filler; every sentence carries decision-relevant information.

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?

With an output schema present, full parameter documentation, and annotations covering safety, the description needs only to define scope and constraints, which it does. The one missing piece is routing guidance against more specific Azure tools, which matters given the crowded sibling set.

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 description coverage is 100%, so all three parameters are already documented in the schema. The description repeats the command-format hint (no leading 'az') and gives example command strings, but adds no new semantics for context_id or azure_tenant_id. 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?

States a specific verb and resource ('executes any read-only Azure CLI command') and bounds the scope with a verb allowlist plus examples. It is clear what the tool does, but never contrasts itself with the many specialized Azure siblings (azure_resource_groups, azure_servicebus_namespaces, azure_blob_find) that cover a subset of the same ground.

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 allowed-verb list ('list, show, get, describe, check, verify…') and the prohibition on write/delete/secret-value operations give real guidance on when the tool is usable. However, there is no instruction on when to prefer a specialized sibling over this generic escape hatch, which is the key routing decision for an agent facing ~200 alternatives.

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

All Opsphere — DevOps & SRE Intelligence tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?