Skip to main content
Glama

what_happened

Generate a newest-first timeline of logs, deploys, alerts, checks, incidents, and metric changes for one service or all services within a 30m–24h window to investigate incidents.

Instructions

What happened to the services in a stretch of time, newest first: log changes, deploys, alerts, checks, incidents and metric steps, each with when it was and what it was. service narrows it to one service. window is how far back to look: 30m, 1h, 6h or 24h. The window ends at around, an ISO time such as 2026-11-02T14:00:00Z (no zone means UTC), which is now when left out. To see what led up to a moment, pass that moment as around.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "what_happened"
  }
}

Input Schema

NameRequiredDescriptionDefault
aroundNo
windowNo30m
serviceNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does reasonably well: it discloses result ordering ("newest first"), the full set of event categories returned, that the window anchors at `around` rather than at the current time, and the no-zone-means-UTC convention. It omits anything about result limits, truncation, permissions, or rate limits, which is a real gap for an unbounded time-range listing.

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?

The scope and the returned event types come first, then the three parameters in a sensible order, then the one non-obvious usage tip. Mostly dense prose with little waste, though "each with when it was and what it was" is a slightly padded restatement of the category list.

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 shape need not be described, and with only three optional parameters and no annotations the description covers what an agent needs to call it correctly. The missing pieces are operational rather than structural: no hint about result volume or whether a wide 24h window over all services returns a bounded list.

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?

Schema description coverage is 0%, so this text is the only documentation, and it covers all three parameters: `service` scopes to one service, `window` accepts 30m/1h/6h/24h, and `around` takes an ISO timestamp defaulting to now with UTC implied. The one soft spot is that the four window values are listed without confirming whether other durations are accepted.

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 gives a specific verb-and-resource framing plus an enumeration of what the timeline contains: "log changes, deploys, alerts, checks, incidents and metric steps." The name is vague on its own, but the text makes clear this is a chronological event-history query. It does not explicitly contrast itself with siblings such as what_is_broken or what_needs_me, which are the nearest neighbours.

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?

Usage is implied rather than stated: "To see what led up to a moment, pass that moment as `around`" is the only intent-level guidance, and `service` is described as narrowing. There is no statement of when to prefer this over what_is_broken/what_needs_me or when a timeline is the wrong view. Adequate but leaves the routing decision to inference.

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