Opsphere — DevOps & SRE Intelligence

Get bounded QA release snapshot

qa_release_snapshot

Read-only

Resolve tenant-scoped QA context first, then collect release, deployment and observability evidence with at most two concurrent provider reads. Returns partial evidence instead of failing the whole investigation.

Input Schema

Name	Required	Description
`hours`	No
`scope`	No	Optional product, site, application, repository or service, resolved only from active-tenant metadata
`target`	No	Exact Cloud Catalog account/product slug for deployment evidence. Separate from scope (QA suites/repository). With target alone, returns deployments but no target-specific QA readiness verdict.
`refresh`	No
`commit_sha`	No
`context_id`	No	Optional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.
`environment`	Yes

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed32 schema fields changedOct 26, 2026

changedOutput schema / properties / data / additionalProperties
```
Previous value: -trueNew value: +false
```
removedOutput schema / properties / data / properties / action
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / data / properties / ambiguous
```
Removed value: -{
-  "type": "boolean"
-}
```
removedOutput schema / properties / data / properties / cached
```
Removed value: -{
-  "type": "boolean"
-}
```

removedOutput schema / properties / data / properties / candidates

Removed value: -{
-  "items": {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  "type": "array"
-}

removedOutput schema / properties / data / properties / catalog / $ref
```
Removed value: -"#/properties/data/properties/candidates/items"
```
addedOutput schema / properties / data / properties / catalog / additionalProperties
```
Added value: +false
```

addedOutput schema / properties / data / properties / catalog / properties

Added value: +{
+  "frameworks": {
+    "items": {
+      "additionalProperties": false,
+      "properties": {
+        "confidence": {
+          "enum": [
+            "high",
+            "medium",
+            "low"
+          ],
+          "type": "string"
+        },
+        "configFiles": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "name": {
+          "type": "string"
+        },
+        "sourceRepositoryId": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "name"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "sources": {
+    "items": {
+      "additionalProperties": false,
+      "properties": {
+        "archived": {
+          "type": "boolean"
+        },
+        "commitSha": {
+          "type": "string"
+        },
+        "confidence": {
+          "$ref": "#/properties/data/properties/catalog/properties/frameworks/items/properties/confidence"
+        },
+        "provider": {
+          "type": "string"
+        },
+        "ref": {
+          "type": "string"
+        },
+        "repository": {
+          "type": "string"
+        },
+        "repositoryId": {
+          "type": "string"
+        },
+        "roles": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "selectionStatus": {
+          "enum": [
+            "auto_selected",
+            "user_confirmed",
+            "candidate",
+            "ambiguous",
+            "rejected",
+            "ignored",
+            "stale"
+          ],
+          "type": "string"
+        },
+        "webUrl": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "provider",
+        "repositoryId",
+        "repository"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  }
+}

addedOutput schema / properties / data / properties / catalog / type
```
Added value: +"object"
```

removedOutput schema / properties / data / properties / ci

Removed value: -{
-  "$ref": "#/properties/data/properties/candidates"
-}

addedOutput schema / properties / data / properties / commitSha

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

removedOutput schema / properties / data / properties / commit_sha

Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}

addedOutput schema / properties / data / properties / deployment

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "branch": {
+      "type": "string"
+    },
+    "environment": {
+      "type": "string"
+    },
+    "label": {
+      "type": "string"
+    },
+    "revision": {
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    },
+    "target": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

changedOutput schema / properties / data / properties / environment / type
```
Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
```

removedOutput schema / properties / data / properties / frameworks

Removed value: -{
-  "$ref": "#/properties/data/properties/candidates"
-}

addedOutput schema / properties / data / properties / generatedAt

Added value: +{
+  "format": "date-time",
+  "type": "string"
+}

removedOutput schema / properties / data / properties / generated_at
```
Removed value: -{
-  "type": "string"
-}
```

removedOutput schema / properties / data / properties / matrix

Removed value: -{
-  "$ref": "#/properties/data/properties/candidates"
-}

removedOutput schema / properties / data / properties / policy_configured
```
Removed value: -{
-  "type": "boolean"
-}
```

removedOutput schema / properties / data / properties / preference

Removed value: -{
-  "$ref": "#/properties/data/properties/candidates/items"
-}

removedOutput schema / properties / data / properties / sections

Removed value: -{
-  "$ref": "#/properties/data/properties/candidates/items"
-}

removedOutput schema / properties / data / properties / selected_repository_ids

Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedOutput schema / properties / data / properties / sources

Removed value: -{
-  "$ref": "#/properties/data/properties/candidates"
-}

removedOutput schema / properties / data / properties / suites

Removed value: -{
-  "$ref": "#/properties/data/properties/candidates"
-}

addedOutput schema / properties / data / properties / target

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

removedOutput schema / properties / data / properties / tenant_id
```
Removed value: -{
-  "type": "string"
-}
```
addedOutput schema / properties / data / properties / truncated
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / data / properties / verdict / enum

Added value: +[
+  "READY",
+  "NOT_READY",
+  "READY_WITH_UNCONFIRMED_POLICY",
+  "BLOCKED_SCOPE_UNRESOLVED",
+  "BLOCKED_TARGET_UNRESOLVED",
+  "BLOCKED_INSUFFICIENT_EVIDENCE"
+]

removedOutput schema / properties / data / properties / workflows

Removed value: -{
-  "$ref": "#/properties/data/properties/candidates"
-}

addedOutput schema / properties / data / required

Added value: +[
+  "environment",
+  "verdict",
+  "partial",
+  "gaps",
+  "truncated",
+  "warnings"
+]

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

A3.5/5.0

Behavior4/5

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

With readOnlyHint/destructiveHint already covering safety, the description adds genuinely new behavior: a concurrency ceiling of two provider reads and a partial-result contract that degrades rather than failing the whole investigation. It does not mention authorization requirements or cost/latency expectations, so it falls short of a 5.

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 sentences, both load-bearing, with the prerequisite and the partial-result guarantee front-loaded. No filler or restatement of the title.

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?

An output schema exists, so return-shape explanation is not required, and annotations cover safety. But for a 7-parameter aggregation tool with low schema coverage, the description leaves the agent guessing on window size, refresh cost, and commit pinning — gaps that matter for correct invocation.

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

Parameters2/5

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

Schema description coverage is only 43%: hours, refresh, commit_sha and the required environment have no descriptions at all. The description does nothing to compensate — it says nothing about what the time window means, what refresh invalidates, or how commit_sha narrows the evidence — despite these being the parameters most likely to be set wrong.

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 ('collect') and resource set (release, deployment and observability evidence) plus a scoping quality ('bounded', 'tenant-scoped'). However, it never distinguishes itself from the obvious sibling qa_release_evidence, which from its name alone appears to overlap heavily, so the agent cannot confidently choose between them.

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?

'Resolve tenant-scoped QA context first' is a useful prerequisite/sequencing hint, and 'Returns partial evidence instead of failing' implies it is the resilient choice for whole-investigation runs. But there is no explicit statement of when to prefer this over qa_release_evidence, qa_sources_discover, or qa_catalog_get, and no when-not-to-use guidance.

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?