Skip to main content
Glama
Sign In

Opsphere — DevOps & SRE Intelligence

by io.opsphere.mcp-cursor
OverviewDiscussionsAdmin

Evaluate QA release evidence

qa_release_evidence
Read-only

Correlate the tenant-scoped QA catalog and optional policy with CI evidence for one environment, optional site/product/service scope, and commit. An unmatched scope is blocked and is never broadened to the tenant.

Input Schema

NameRequiredDescriptionDefault
scopeNoOptional site, product, application, repository, or service qualifier
refreshNo
commit_shaNo
context_idNoOptional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.
environmentNo

Output Schema

NameRequiredDescriptionDefault
okYes
dataYes
contractVersionYes
dataSchemaVersionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed27 schema fields changed
    • 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
      Removed value: -{
-  "$ref": "#/properties/data/properties/candidates/items"
-}
    • 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"
-  ]
-}
    • removedOutput schema / properties / data / properties / frameworks
      Removed value: -{
-  "$ref": "#/properties/data/properties/candidates"
-}
    • removedOutput schema / properties / data / properties / generated_at
      Removed value: -{
-  "type": "string"
-}
    • removedOutput schema / properties / data / properties / matrix
      Removed value: -{
-  "$ref": "#/properties/data/properties/candidates"
-}
    • addedOutput schema / properties / data / properties / policyConfigured
      Added value: +{
+  "type": "boolean"
+}
    • 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"
-}
    • addedOutput schema / properties / data / properties / scopePolicyConfigured
      Added value: +{
+  "type": "boolean"
+}
    • 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"
-}
    • 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",
+  "scope",
+  "commitSha",
+  "verdict",
+  "policyConfigured",
+  "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"
+]
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare a safe read-only, closed-world operation, so the safety burden is light. The description adds one genuinely useful behavioral rule: an unmatched scope is blocked and never broadened to the tenant, which prevents an agent from trying to fan out. It says nothing about refresh semantics, caching, or how the correlation result is judged.

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?

Two tight sentences with no filler; the core action and the scoping dimension come first and the blocking rule second. Dense but appropriately sized for the tool's complexity.

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 values need not be explained, and the blocking behavior is disclosed. However, with five parameters and zero required fields, the description should say what minimum input is needed to succeed (environment at least) and whether optional policy/refresh alter the verdict.

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 40%, so compensation is expected. The description gives meaning to environment ("one environment"), scope ("optional site/product/service scope"), and commit, but leaves refresh and context_id entirely to the schema, and does not clarify that no parameter is formally required despite environment being semantically necessary.

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 uses a specific verb+resource ("Correlate the tenant-scoped QA catalog and optional policy with CI evidence") and names the scoping dimensions (environment, site/product/service, commit). It is clearly distinguishable from qa_catalog_get and qa_sources_discover, but it never names a sibling to sharpen the boundary.

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?

Usage is only implied: the agent must infer that this is the evaluation step that consumes the catalog/policy and CI evidence. There is no statement of when to pick this over qa_release_snapshot or qa_catalog_get, and no prerequisites (e.g., catalog must already exist) are stated.

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 toolsInspect
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