Opsphere — DevOps & SRE Intelligence

List integration status

ops_list_integrations

Read-only

Shows which provider integrations are configured, available to connect, require upgrade, or are unavailable (beta/enterprise). Availability is derived from PostgreSQL plan entitlements and technical catalog maturity — not from the credential catalog alone. Credential values are never revealed — only masked previews. Only offer "Configure my [Provider]" for providers with configure_cta=true / summary.available_to_connect.

Input Schema

Name	Required	Description	Default
`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.

Changed6 schema fields changedOct 26, 2026

changedOutput schema / properties / data / additionalProperties
```
Previous value: -trueNew value: +false
```

changedOutput schema / properties / data / properties / items / items / additionalProperties

Previous value: -trueNew value: +{
+  "type": [
+    "string",
+    "number",
+    "boolean",
+    "null"
+  ]
+}

removedOutput schema / properties / data / properties / items / items / properties
```
Removed value: -{}
```
addedOutput schema / properties / data / properties / payloadJson
```
Added value: +{
+  "type": "string"
+}
```

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

A4.4/5.0

Behavior5/5

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

Goes well beyond the readOnly/non-destructive annotations by explaining that availability is derived from PostgreSQL plan entitlements and catalog maturity rather than the credential catalog alone — a non-obvious sourcing caveat an agent could otherwise misread. It also reassures that credential values are never revealed, only masked previews, which is meaningful security context for a status endpoint.

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?

Three front-loaded sentences with no filler; the status enumeration comes first and the actionability rule last. Slightly dense with internal terminology ('catalog maturity', 'configure_cta'), but every sentence carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description needn't document return shapes, yet it still flags the two output fields that drive behavior. Combined with the derivation logic and privacy note, an agent has everything needed to call it and act on results.

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?

The single context_id parameter has 100% schema description coverage, so the schema already explains the ctx_* semantics and the omit-to-use-active-workspace default. The description adds nothing about the parameter, which is acceptable at this coverage level but not additive.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Shows which provider integrations are configured, available to connect, require upgrade, or are unavailable') and enumerates the exact status states returned. This clearly separates it from mutating siblings like ops_configure_integration and ops_remove_integration.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an actionable rule for downstream behavior: only offer 'Configure my [Provider]' when configure_cta=true / summary.available_to_connect. It does not name explicit alternatives (e.g., ops_accounts_list) or say when not to call it, so it stops short of full when/when-not 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?