Opsphere — DevOps & SRE Intelligence

Azure Service Bus Queue Metrics

azure_servicebus_queue_metrics

Read-only

Gets detailed metrics of a queue (messages, status, configuration)

Input Schema

Name	Required	Description
`namespace`	Yes	Service Bus namespace name
`queueName`	Yes	Queue name
`context_id`	No	Optional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.
`resourceGroup`	No	Resource Group (optional)
`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.

Changed19 schema fields changedOct 26, 2026
- changedOutput schema / properties / data / additionalProperties
```
Previous value: -trueNew value: +false
```
- addedOutput schema / properties / data / properties / activeMessageCount
```
Added value: +{
+  "type": "integer"
+}
```
- removedOutput schema / properties / data / properties / count
```
Removed value: -{
-  "type": "number"
-}
```
- addedOutput schema / properties / data / properties / deadLetterMessageCount
```
Added value: +{
+  "type": "integer"
+}
```
- addedOutput schema / properties / data / properties / gaps
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```
- removedOutput schema / properties / data / properties / items
```
Removed value: -{
-  "items": {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  "type": "array"
-}
```
- addedOutput schema / properties / data / properties / namespace
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / data / properties / nextLink
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / data / properties / partial
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / data / properties / queueName
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / data / properties / resourceGroup
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / data / properties / sizeInBytes
```
Added value: +{
+  "type": "number"
+}
```
- removedOutput schema / properties / data / properties / subscriptionId
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / data / properties / truncated
```
Added value: +{
+  "type": "boolean"
+}
```
- removedOutput schema / properties / data / properties / value
```
Removed value: -{
-  "$ref": "#/properties/data/properties/items"
-}
```
- addedOutput schema / properties / data / properties / warnings
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```
- addedOutput schema / properties / data / required
```
Added value: +[
+  "namespace",
+  "queueName",
+  "partial",
+  "truncated",
+  "warnings",
+  "gaps"
+]
```
- addedOutput schema / properties / dataSchemaVersion
```
Added value: +{
+  "const": 2,
+  "type": "number"
+}
```
- changedOutput schema / required
```
Previous value: -[
-  "contractVersion",
-  "ok",
-  "data"
-]New value: +[
+  "contractVersion",
+  "dataSchemaVersion",
+  "ok",
+  "data"
+]
```
First observedOct 15, 2026

TDQS

B3.3/5.0

Behavior3/5

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

The annotations already establish that this is a safe, read-only, non-destructive operation, so the description does not need to carry the full safety burden. It adds that the result covers messages, status, and configuration, but it does not disclose whether queue existence is required or how detailed or fresh the metrics are.

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?

The description is a single front-loaded sentence with no filler. The parenthetical list efficiently clarifies the scope of 'detailed metrics' without adding unnecessary length.

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 read-only metrics tool with full schema coverage, annotations, and an output schema, the description is minimally adequate. However, it does not help an agent choose this tool over closely related Service Bus queue tools or clarify what distinguishes these metrics from monitoring or health reports.

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 every parameter is already documented in the input schema. The description does not add any further meaning about required parameters such as namespace and queueName or optional context/resource-group scoping, so the baseline score of 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?

The description states a clear verb and resource: gets detailed metrics of a queue, with parenthetical examples of what those metrics include. It is distinguishable from generic queue-listing siblings, but it does not explicitly differentiate itself from other Service Bus queue-level tools such as queue_deadletter, monitoring_report, or health_overview.

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?

There is no guidance on when to use this tool versus alternatives. Given the many adjacent Service Bus tools, an agent must infer from the name whether this is for health, monitoring, dead-letter, or general queue inspection.

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?