Skip to main content
Glama
Sign In

Opservo

by com.getopservo
OverviewDiscussionsAdmin

Incident timeline

get_incident_timeline
Read-onlyIdempotent

Returns a time-ordered list of correlated events on one server over a look-back window — service crashes, error and warning spikes in the logs, CPU/memory/disk thresholds crossed, SSL certificates nearing expiry, and newly detected issues — with the likely root cause when one is identified.

Input Schema

NameRequiredDescriptionDefault
hoursNoLook-back window in hours, 1 to 720 (default 4).
agent_idYesThe server/agent UUID to query.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent only when the call failed: why, in plain English (unknown server, server from another workspace, not a Kubernetes cluster).
eventsNoCorrelated events, oldest first.
root_causeNoThe event the others are attributed to, or null.
window_endNoEnd of the look-back window, ISO 8601.
window_startNoStart of the look-back window, ISO 8601.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "error": {
+      "description": "Present only when the call failed: why, in plain English (unknown server, server from another workspace, not a Kubernetes cluster).",
+      "type": "string"
+    },
+    "events": {
+      "description": "Correlated events, oldest first.",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "caused_by": {
+            "description": "Id of the event this one is attributed to, when a cause was identified.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "detail": {
+            "description": "What was observed.",
+            "type": "string"
+          },
+          "id": {
+            "description": "Event id, unique within the timeline.",
+            "type": "string"
+          },
+          "service": {
+            "description": "Service involved, if any.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "timestamp": {
+            "description": "When the event happened, ISO 8601.",
+            "type": "string"
+          },
+          "title": {
+            "description": "One-line title.",
+            "type": "string"
+          },
+          "type": {
+            "description": "Event type: service_crash, error_spike, warning_spike, metric_threshold, ssl_expiry, recommendation or similar.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "timestamp",
+          "type",
+          "title"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "root_cause": {
+      "additionalProperties": true,
+      "description": "The event the others are attributed to, or null.",
+      "properties": {
+        "caused_by": {
+          "description": "Id of the event this one is attributed to, when a cause was identified.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "detail": {
+          "description": "What was observed.",
+          "type": "string"
+        },
+        "id": {
+          "description": "Event id, unique within the timeline.",
+          "type": "string"
+        },
+        "service": {
+          "description": "Service involved, if any.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "timestamp": {
+          "description": "When the event happened, ISO 8601.",
+          "type": "string"
+        },
+        "title": {
+          "description": "One-line title.",
+          "type": "string"
+        },
+        "type": {
+          "description": "Event type: service_crash, error_spike, warning_spike, metric_threshold, ssl_expiry, recommendation or similar.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "timestamp",
+        "type",
+        "title"
+      ],
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "window_end": {
+      "description": "End of the look-back window, ISO 8601.",
+      "type": "string"
+    },
+    "window_start": {
+      "description": "Start of the look-back window, ISO 8601.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  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 the tool as read-only, idempotent, non-destructive, and closed-world. The description adds no further behavioral traits such as auth requirements, rate limits, or performance characteristics, but it does provide clarity on the correlated nature of the output. With rich annotations, the bar is lower, and this is adequate.

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?

The description is a single, well-structured sentence that front-loads the core action and lists relevant event types without any wasted words. Every element contributes to understanding the tool's scope.

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?

Given the presence of an output schema and comprehensive annotations, the description is nearly complete for the tool's purpose. It could be improved by explicitly noting when to use it over related tools, but it is otherwise sufficient for correct invocation.

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%, and both parameters (agent_id, hours) are fully documented in the schema. The description does not add any parameter meaning, so the baseline of 3 is appropriate.

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 names a specific verb ('Returns') and resource ('time-ordered list of correlated events on one server'), and enumerates the event types it captures. It is clear and detailed, but it does not explicitly distinguish itself from siblings like get_log_summary or get_recommendations.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The description only states what it returns, leaving the agent to infer usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Opservo toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources