Opsphere — DevOps & SRE Intelligence

Resumen de salud del entorno

env_health_summary

Read-only

Devuelve un resumen estructurado del estado general de un entorno (INT, TST, PRE, PRD) en las últimas N horas, incluyendo errores, salud de pods, latencia y eventos relevantes de despliegue. El resultado incluye _signatureAscii: un gráfico ASCII para CLI/IDE. Incluye siempre el contenido de _signatureAscii al final de tu respuesta en un bloque de código (```text) para que el usuario vea el gráfico.

Input Schema

Name	Required	Description
`env`	Yes	Nombre del entorno (INT, TST, PRE, PRD, etc.)
`hours`	No	Ventana temporal hacia atrás en horas
`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.

Changed27 schema fields changedOct 26, 2026

changedOutput schema / properties / data / additionalProperties
```
Previous value: -trueNew value: +false
```
addedOutput schema / properties / data / properties / _signatureAscii
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / data / properties / capacity

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "anyPressure": {
+      "type": "boolean"
+    },
+    "notes": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "anyPressure"
+  ],
+  "type": "object"
+}

removedOutput schema / properties / data / properties / count
```
Removed value: -{
-  "type": "number"
-}
```

removedOutput schema / properties / data / properties / data

Removed value: -{
-  "anyOf": [
-    {
-      "$ref": "#/properties/data/properties/items"
-    },
-    {
-      "$ref": "#/properties/data/properties/items/items"
-    }
-  ]
-}

addedOutput schema / properties / data / properties / deployments

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "notes": {
+        "type": "string"
+      },
+      "service": {
+        "type": "string"
+      },
+      "status": {
+        "type": "string"
+      },
+      "timestamp": {
+        "type": "string"
+      },
+      "version": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "service",
+      "version",
+      "timestamp",
+      "status"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / data / properties / env
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / data / properties / error

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "$ref": "#/properties/data/properties/items/items"
-    }
-  ]
-}

addedOutput schema / properties / data / properties / errors

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "topServices": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "errorCount": {
+            "type": "number"
+          },
+          "rate": {
+            "type": "number"
+          },
+          "service": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "service"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "totalErrorRate": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "totalErrorRate",
+    "topServices"
+  ],
+  "type": "object"
+}

removedOutput schema / properties / data / properties / items

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

addedOutput schema / properties / data / properties / kubernetes

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "nodes": {
+      "additionalProperties": false,
+      "properties": {
+        "ready": {
+          "type": "number"
+        },
+        "total": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "ready",
+        "total"
+      ],
+      "type": "object"
+    },
+    "pods": {
+      "additionalProperties": false,
+      "properties": {
+        "failed": {
+          "type": "number"
+        },
+        "pending": {
+          "type": "number"
+        },
+        "running": {
+          "type": "number"
+        },
+        "succeeded": {
+          "type": "number"
+        },
+        "total": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "running",
+        "pending",
+        "failed",
+        "succeeded",
+        "total"
+      ],
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / data / properties / latency

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "comments": {
+      "type": "string"
+    },
+    "trend": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "trend"
+  ],
+  "type": "object"
+}

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

removedOutput schema / properties / data / properties / meta

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

removedOutput schema / properties / data / properties / nextCursor

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

addedOutput schema / properties / data / properties / noteworthyEvents

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

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

removedOutput schema / properties / data / properties / pageInfo

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

removedOutput schema / properties / data / properties / results

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

changedOutput schema / properties / data / properties / status / type

Previous value: -[
-  "string",
-  "number"
-]New value: +"string"

removedOutput schema / properties / data / properties / text
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / data / properties / total
```
Removed value: -{
-  "type": "number"
-}
```

addedOutput schema / properties / data / properties / uptime

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "checks": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "hostname": {
+            "type": "string"
+          },
+          "id": {
+            "type": "number"
+          },
+          "name": {
+            "type": "string"
+          },
+          "status": {
+            "type": "string"
+          },
+          "uptimePercent": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "id",
+          "status"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "downCount": {
+      "type": "number"
+    },
+    "source": {
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "source",
+    "status",
+    "downCount"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / data / properties / windowHours
```
Added value: +{
+  "type": "number"
+}
```

addedOutput schema / properties / data / required

Added value: +[
+  "status",
+  "env",
+  "windowHours"
+]

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.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description goes further by naming the returned dimensions and disclosing a _signatureAscii artifact plus a mandatory convention for surfacing it to the user. It stops short of stating data sources, freshness, or any cost/latency caveats for a tool that fans out across errors, pods, latency and deploys.

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 sentences, front-loaded with the purpose and return scope before the ASCII directive. The final sentence is longer than needed but carries an operational instruction the agent must follow, so it earns its place.

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-value detail is not owed, and the description correctly spends its budget on the one thing the schema cannot convey: the ASCII signature and how to present it. Nothing critical is missing for calling a read-only summary tool with three self-documented parameters.

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 100%, so the schema already documents env, hours (1-168, default 24) and context_id. The description only echoes these, restating the env names and the 'últimas N horas' window without adding new semantics such as how invalid or empty windows behave. Baseline 3 applies.

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 and resource ('Devuelve un resumen estructurado del estado general de un entorno') and enumerates the sections included (errores, salud de pods, latencia, eventos de despliegue), which makes its breadth self-evident. It never names the closer-grained siblings env_errors_overview or env_capacity_overview, so the agent must infer that this is the rollup option rather than the targeted one.

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?

No explicit when-to-use or when-not-to-use guidance against alternatives; usage is only implied by the phrase 'estado general'. The only imperative given is about output presentation ('Incluye siempre el contenido de _signatureAscii...'), which is a response-handling rule, not selection 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?