Skip to main content
Glama
Flux159
by Flux159

kubectl_logs

Read-only

Fetch logs from Kubernetes resources such as pods, deployments, and jobs. Supports tail, since time, timestamps, and container selection.

Instructions

Get logs from Kubernetes resources like pods, deployments, or jobs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
resourceTypeYesType of resource to get logs from
nameYesName of the resource
namespaceYesKubernetes namespacedefault
containerNoContainer name (required when pod has multiple containers)
tailNoNumber of lines to show from end of logs
sinceNoShow logs since relative time (e.g. '5s', '2m', '3h')
sinceTimeNoShow logs since absolute time (RFC3339)
timestampsNoInclude timestamps in logs
previousNoInclude logs from previously terminated containers
followNoFollow logs output (not recommended, may cause timeouts)
labelSelectorNoFilter resources by label selector
contextNoKubeconfig Context to use for the command (optional - defaults to null)
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description aligns with a read-only operation. It adds the resource type constraint but does not disclose other behaviors like timeout risks for follow, which is mentioned only in the schema parameter.

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?

Single sentence, front-loaded with verb and resource, no unnecessary words.

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?

Description captures core purpose adequately for a read-only tool with full schema coverage. Could benefit from mentioning that logs are text output or the follow parameter caution, but not critical.

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 documents all parameters. The description adds no additional meaning or clarification for parameters.

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?

Description clearly states the verb 'Get' and resource 'logs from Kubernetes resources', with specific examples (pods, deployments, jobs). This distinguishes it from siblings like kubectl_describe or exec_in_pod.

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?

No guidance on when to use this tool vs alternatives (e.g., kubectl_describe for details, exec_in_pod for interactive access). No exclusion criteria or when-not-to-use information.

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/Flux159/mcp-server-kubernetes'

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