Skip to main content
Glama

get-events

Retrieve Kubernetes events to identify and resolve cluster issues, enabling efficient troubleshooting of pods, deployments, and services.

Instructions

Get Kubernetes events for troubleshooting

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
namespaceNoThe namespace to get events from (optional, defaults to current context namespace)

Implementation Reference

  • Executes the 'get-events' tool by running the kubectl get events command, optionally filtered by namespace, sorted by last timestamp, and returns the output as text content.
    case "get-events": {
      const { namespace } = args || {};
      const nsArg = namespace ? `-n ${namespace}` : "";
      const cmd = `kubectl get events ${nsArg} --sort-by='.lastTimestamp'`;
      const { stdout } = await execAsync(cmd);
      return {
        content: [{ type: "text", text: stdout || "No events found" }]
      };
    }
  • Defines the tool metadata including name, description, and input schema allowing an optional namespace parameter.
      name: "get-events",
      description: "Get Kubernetes events for troubleshooting",
      inputSchema: {
        type: "object",
        properties: {
          namespace: { 
            type: "string",
            description: "The namespace to get events from (optional, defaults to current context namespace)"
          }
        }
      }
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'Get' implies a read operation, but it doesn't disclose behavioral traits like whether this requires specific permissions, how events are formatted/returned, if there are rate limits, or if it's a real-time vs historical query. The description is minimal and leaves critical behavioral aspects unspecified.

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 description is a single, efficient sentence that gets straight to the point with no wasted words. However, it's arguably too concise given the lack of behavioral context and usage guidance needed for this tool category.

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

Completeness2/5

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

For a Kubernetes troubleshooting tool with no annotations and no output schema, the description is insufficient. It doesn't explain what constitutes an 'event', how results are structured, what time range is covered, or any limitations. Given the complexity of Kubernetes environments and the rich sibling toolset, more context is needed for effective use.

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 the optional 'namespace' parameter with its default behavior. The description adds no parameter information beyond what's in the schema, maintaining the baseline score of 3 since the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get Kubernetes events for troubleshooting' clearly states the verb ('Get') and resource ('Kubernetes events'), but it's vague about scope and doesn't distinguish from sibling tools like 'describe-pod' or 'get-logs' that might also be used for troubleshooting. It specifies the purpose but lacks precision about what 'events' means in this context.

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?

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools available for Kubernetes troubleshooting (e.g., 'describe-pod', 'get-logs', 'list-pods'), there's no indication of when this specific event-fetching tool is appropriate or what problems it's best suited for.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/thekaranpargaie/kube-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server