k8s-mcp

k8s_pod_logs

Read the tail of a Kubernetes pod's log to review recent output. Specify pod name, container, namespace, and number of lines to fetch.

Instructions

Read the tail of a pod log.

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": {
      "pod": "<pod>"
    },
    "name": "k8s_pod_logs"
  }
}

Input Schema

Name	Required	Default
`pod`	Yes
`tail`	No
`container`	No
`namespace`	No
`session_name`	No	default

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 24, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations present, the description carries the full behavioral burden, but only states that it reads the tail. It does not disclose whether logs are streamed or truncated, how container selection works, whether a connection is required, or what happens on failure.

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?

One short sentence that is front-loaded with the key verb, resource, and scope. There is no redundant or filler text, and the wording is immediately parseable.

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

Completeness3/5

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

For a simple read tool with only one required parameter plus schema defaults and an output schema, the description is minimally viable. However, it omits practical invocation context such as selecting a container inside a multi-container pod and whether a prior connection/session is assumed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It clarifies the 'pod' and 'tail' concepts only implicitly and says nothing about the semantics or interplay of container, namespace, and session_name.

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 names a concrete action ('Read'), a specific resource ('pod log'), and a defined scope ('tail'). This cleanly separates it from sibling listing tools such as k8s_list_pods and k8s_events.

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 gives no guidance on when to select this tool over alternatives, such as k8s_events for cluster diagnostics or k8s_connect for establishing a session. There is no when-to-use or when-not-to-use statement.

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

Deploy Server