Opsphere — DevOps & SRE Intelligence

Discover QA sources

qa_sources_discover

Read-only

Discover read-only QA repositories in the active workspace using technical evidence; no repository configuration or code execution.

Input Schema

Name	Required	Description	Default
`refresh`	No
`context_id`	No	Optional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed31 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

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

removedOutput schema / properties / data / properties / ci

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

removedOutput schema / properties / data / properties / commit_sha

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

removedOutput schema / properties / data / properties / environment

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

addedOutput schema / properties / data / properties / family

Added value: +{
+  "const": "quality",
+  "type": "string"
+}

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 / operation

Added value: +{
+  "const": "qa_sources_discover",
+  "type": "string"
+}

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 / records

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "confidence": {
+        "type": "string"
+      },
+      "createdAt": {
+        "type": "string"
+      },
+      "environment": {
+        "type": "string"
+      },
+      "facts": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "name": {
+              "type": "string"
+            },
+            "value": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "number"
+                },
+                {
+                  "type": "boolean"
+                },
+                {
+                  "type": "null"
+                },
+                {
+                  "items": {
+                    "type": [
+                      "string",
+                      "number",
+                      "boolean",
+                      "null"
+                    ]
+                  },
+                  "type": "array"
+                }
+              ]
+            }
+          },
+          "required": [
+            "name",
+            "value"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "id": {
+        "type": "string"
+      },
+      "key": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "provider": {
+        "type": "string"
+      },
+      "repository": {
+        "type": "string"
+      },
+      "status": {
+        "type": "string"
+      },
+      "summary": {
+        "type": "string"
+      },
+      "tags": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "title": {
+        "type": "string"
+      },
+      "type": {
+        "type": "string"
+      },
+      "updatedAt": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "facts"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

removedOutput schema / properties / data / properties / scope

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

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 / summary
```
Added value: +{
+  "type": "string"
+}
```
removedOutput schema / properties / data / properties / tenant_id
```
Removed value: -{
-  "type": "string"
-}
```

addedOutput schema / properties / data / properties / total

Added value: +{
+  "minimum": 0,
+  "type": "integer"
+}

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

removedOutput schema / properties / data / properties / workflows

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

addedOutput schema / properties / data / required

Added value: +[
+  "family",
+  "operation",
+  "records",
+  "total",
+  "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.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is known. The description reinforces it and adds useful scope ('no repository configuration or code execution'), meaning it works without setup, but says nothing about caching, refresh behavior, or cost/latency of discovery.

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?

A single front-loaded sentence with the resource and scope first and the constraint clause after. It wastes nothing, though 'using technical evidence' is slightly opaque phrasing rather than informative.

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?

Output schema exists, so return values needn't be explained. But for a discovery tool with an unexplained 'refresh' parameter and no mention of how evidence is gathered or what a discovered 'source' is, the description leaves gaps an agent must resolve by trial.

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 coverage is only 50%: context_id is documented in the schema, but 'refresh' has no description anywhere and the prose says nothing about it, so the agent has to guess whether re-discovery is cached or forced. The description adds no parameter meaning beyond the schema.

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+resource ('Discover read-only QA repositories') and scope ('in the active workspace'), which is clear. It does not differentiate from the related qa_catalog_get / qa_release_evidence / qa_release_snapshot siblings, so an agent can't tell from the description alone whether discovery is a prerequisite for those or an alternative.

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?

'Discover' plus 'using technical evidence' implies a pre-step before catalog/release lookups, but the description never says when to call this instead of the other qa_* tools or what a caller should do with the result. Usage is inferable but not 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 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?