Skip to main content
Glama

Resource timeline

resource_timeline
Read-only

Show the state-transition history of one Kubernetes resource over a time window (default 48h, max 14 days): when it was created/deleted, status changes, container restarts, scaling events, and spec changes, each timestamped. Use this to answer 'since when has this been failing/flapping', to find when a regression started, and to correlate with deploys (get_execution_trends) or events (get_events). Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "kind": "<kind>",
      "name": "<name>",
      "cluster_id": "<cluster_id>"
    },
    "name": "resource_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesKubernetes kind, e.g. Pod, Deployment, StatefulSet.
nameYesResource name.
namespaceNoNamespace (optional for cluster-scoped kinds).
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
window_hoursNoLook-back window in hours (default 48, max 336 = 14 days).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and "Read-only." simply restates it. The description does add genuinely useful context beyond annotations: the event categories returned, that each entry is timestamped, and the default/maximum look-back window, but says nothing about volume of results, pagination, or what happens for a resource with no recorded transitions.

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?

Front-loaded with the core definition, then a purpose sentence, with zero filler. The parenthetical enumeration is long but every item is a distinct event category an agent would want when deciding whether to call this tool.

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?

A read-only query tool with three required identifiers, full schema coverage, and no output schema; the description covers what it returns at a category level and the time-bound semantics. Only the response shape (ordering, per-entry fields, size) is left to be discovered at call time, which is acceptable given no output schema is declared.

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 coverage is 100%, so every parameter (including the kind/name/cluster_id triple and the list_clusters discovery hint for cluster_id) is already documented. The description restates the 48h default and 14-day cap that window_hours already specifies, adding no format or selection guidance beyond the schema; baseline 3 applies.

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 ("state-transition history of one Kubernetes resource") plus an explicit scope (time window with default 48h / max 14 days). It then enumerates exactly which transition types are covered (created/deleted, status changes, container restarts, scaling events, spec changes), which no sibling tool name implies on its own.

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 concrete use cases ("since when has this been failing/flapping", finding when a regression started) and names two sibling tools to correlate with (get_execution_trends, get_events). It does not state exclusions against the closest neighbours, such as describe_resource for current state or get_application_timeline for app-level history, so the agent must still infer that boundary.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.