Skip to main content
Glama
Sign In

Opsphere — DevOps & SRE Intelligence

by io.opsphere.mcp-cursor
OverviewDiscussionsAdmin

List linked accounts

ops_accounts_list
Read-only

Connection Hub only. List active linked tenant connections (id, label, tenant slug, status) for the authenticated Hub owner.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
okYes
dataYes
contractVersionYes
dataSchemaVersionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedOutput schema / properties / data / properties / accounts / items / additionalProperties
      Previous value: -{
-  "type": [
-    "string",
-    "number",
-    "boolean",
-    "null"
-  ]
-}New value: +false
    • addedOutput schema / properties / data / properties / accounts / items / properties
      Added value: +{
+  "display_name": {
+    "type": "string"
+  },
+  "id": {
+    "type": "string"
+  },
+  "label": {
+    "type": "string"
+  },
+  "linked_at": {
+    "type": "string"
+  },
+  "status": {
+    "type": "string"
+  },
+  "tenant": {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "type": "string"
+      },
+      "slug": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "id",
+      "slug"
+    ],
+    "type": "object"
+  }
+}
    • addedOutput schema / properties / data / properties / accounts / items / required
      Added value: +[
+  "id",
+  "label",
+  "tenant",
+  "status",
+  "display_name",
+  "linked_at"
+]
    • removedOutput schema / properties / data / properties / connections / $ref
      Removed value: -"#/properties/data/properties/accounts"
    • addedOutput schema / properties / data / properties / connections / items
      Added value: +{
+  "$ref": "#/properties/data/properties/accounts/items"
+}
    • addedOutput schema / properties / data / properties / connections / type
      Added value: +"array"
    • changedOutput schema / properties / data / properties / error / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "$ref": "#/properties/data/properties/accounts/items"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "additionalProperties": {
+      "type": [
+        "string",
+        "number",
+        "boolean",
+        "null"
+      ]
+    },
+    "type": "object"
+  }
+]
  2. Changed6 schema fields changed
    • changedOutput schema / properties / data / additionalProperties
      Previous value: -trueNew value: +false
    • changedOutput schema / properties / data / properties / accounts / items / additionalProperties
      Previous value: -trueNew value: +{
+  "type": [
+    "string",
+    "number",
+    "boolean",
+    "null"
+  ]
+}
    • removedOutput schema / properties / data / properties / accounts / items / properties
      Removed value: -{}
    • addedOutput schema / properties / data / properties / connection
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "display_name": {
+      "type": "string"
+    },
+    "tenant_id": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • addedOutput schema / properties / dataSchemaVersion
      Added value: +{
+  "const": 1,
+  "type": "number"
+}
    • changedOutput schema / required
      Previous value: -[
-  "contractVersion",
-  "ok",
-  "data"
-]New value: +[
+  "contractVersion",
+  "dataSchemaVersion",
+  "ok",
+  "data"
+]
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral facts: results are scoped to the authenticated Hub owner and only 'active' connections are returned. It doesn't mention pagination or empty-result behavior, keeping it below 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?

One sentence, front-loaded with the domain constraint and the verb, and the parenthetical enumerates return fields compactly. Nothing is wasted.

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

Completeness4/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 no prose. For a zero-parameter read tool with full annotation coverage, the description supplies the missing scope and ownership context, though it omits pagination/limit behavior and how errors surface when the caller isn't a Hub owner.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4. The description usefully clarifies that no filtering arguments exist because scoping is fixed to the authenticated owner.

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 ('List') and resource ('active linked tenant connections') plus the exact fields returned and a domain constraint ('Connection Hub only'). An agent can distinguish this from siblings like ops_list_integrations or ops_account_link_start without reading the schema.

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?

The 'Connection Hub only' qualifier implies the usage context and implicitly excludes non-Hub deployments, but it never names an alternative or states explicit when/when-not conditions. Guidance is inferable rather than 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