KubeCraft MCP Server

Get Events

get_events

Fetch recent Kubernetes events filtered by namespace, resource, or event type to monitor cluster activity.

Instructions

Fetch recent Kubernetes events, optionally filtered by namespace, resource, or type.

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": "get_events"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max events to return (default: 50)
`namespace`	No	Filter by namespace (omit for all namespaces)
`event_type`	No	Filter by event type
`resource_name`	No	Filter to events involving this resource name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 13, 2026

TDQS

B3.3/5.0

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. It only says 'Fetch recent Kubernetes events' without disclosing if the operation is read-only, what 'recent' means, or any side effects. There is no mention of pagination or rate limits.

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, front-loaded sentence with no wasted words. It could benefit from additional details like return format, but is appropriately concise for a simple tool.

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?

Given 4 parameters, no output schema, and no annotations, the description lacks context about return format, ordering, time range for 'recent', and what constitutes a 'resource'. The tool is relatively simple but still incomplete for an agent to use effectively without guessing.

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 baseline is 3. The description lists the filter options aligning with schema properties. However, it adds only the word 'recent' beyond what the schema already provides via parameter descriptions and defaults.

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 uses a specific verb 'Fetch' and resource 'Kubernetes events', and mentions optional filters (namespace, resource, type). This clearly distinguishes from sibling tools like list_pods or get_pod_logs.

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?

The description implies usage for fetching events with filters, but does not explicitly state when to use this tool over alternatives or provide exclusions (e.g., 'For pod logs use get_pod_logs').

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

Deploy Server