Skip to main content
Glama

Get events

get_events
Read-only

Fetch Kubernetes events (Normal/Warning) as summary rows: type, reason, message (cut to 200 characters; message_truncated says when), involved object, count, first and last timestamp. Warning events sort first, newest first within each type. A list needs namespace, an involved_object_name, or all_namespaces=true, and carries total, returned, truncated and scope. Events reveal why pods fail, deployments stall, and what errors occurred.

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": {
      "cluster_id": "<cluster_id>"
    },
    "name": "get_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of events to return.
namespaceNoKubernetes namespace to list events from. A list needs this, an involved_object_name, or all_namespaces=true.
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
all_namespacesNoSet true to list every namespace on the cluster deliberately. Omit it and pass namespace to list one namespace; a list with neither is refused (error_code scope_required).
involved_object_kindNoFilter events by resource kind (e.g., 'Pod', 'Deployment').
involved_object_nameNoFilter events related to a specific resource name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses important behavioral traits: Warning events sort first, newest first within each type, messages are truncated to 200 characters with message_truncated indicating truncation, and the response carries total, returned, truncated, and scope metadata. This is exactly the kind of output-shape and behavior detail an agent needs, especially since no output schema exists.

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 front-loaded with the core operation and return shape, then adds sorting, scope requirements, and use-case context in a tight sequence. Every sentence contributes useful information, and there is no filler or repetition that does not earn its place.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only Kubernetes event listing tool with no output schema, the description is complete enough to call correctly: it explains the returned summary fields, truncation behavior, sort order, required list scope, and response metadata. The remaining details, such as cluster ID discovery, are already covered by the input schema.

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 input schema already documents all six parameters well, including the scope_required error for all_namespaces. The description restates the namespace / involved_object_name / all_namespaces scope rule but adds no new parameter syntax or formatting details beyond the schema, so the baseline 3 is appropriate.

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?

The description opens with a specific verb and resource: 'Fetch Kubernetes events (Normal/Warning) as summary rows.' It names exactly what is returned, including type, reason, message truncation, involved object, count, and timestamps, which clearly distinguishes it from sibling tools such as get_pods, get_pod_logs, and describe_resource.

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?

It gives a clear use case — events reveal why pods fail, deployments stall, and what errors occurred — and states the scope requirement for a valid list. It does not explicitly name alternatives or when-not-to-use cases, so it falls short of the highest level, but the context is strong enough for an agent to select it correctly.

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.