Skip to main content
Glama
vijaykodam

Kubernetes Read Only MCP Server

by vijaykodam

Get Logs

get_logs
Read-onlyIdempotent

Retrieve logs from Kubernetes pods, deployments, jobs, or resources filtered by label selector, with options for container selection, line count, time range, and timestamps.

Instructions

Get logs from pods, deployments, jobs, or resources matching a label selector

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
resource_typeYesType of resource to get logs from ('pod', 'deployment', 'job', etc.)
namespaceNoThe Kubernetes namespace. If not provided and name is specified, uses the 'default' namespace. If neither name nor namespace is provided, searches across all namespaces.
nameNoThe name of the specific resource to get logs from.
label_selectorNoLabel selector to filter resources (e.g. 'app=nginx'). Required if name is not provided.
containerNoThe container name within the pod. If not specified and the pod has multiple containers, logs from the first container will be returned.
tailNoNumber of lines to show from the end of the logs.
since_secondsNoReturn logs newer than a relative duration in seconds.
timestampsNoInclude timestamps at the beginning of each line. Default is False.
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description does not add behavioral details such as log format, truncation limits, or response structure, but it is consistent and does not contradict annotations.

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, focused sentence with no redundant wording. Front-loaded with verb and resource types.

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?

For an 8-parameter read tool with complete schema coverage and annotations, the description provides essential context. Missing mention of return value format (e.g., text stream) but schema fills most gaps.

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% with detailed parameter descriptions. The tool description (one sentence) does not add extra meaning beyond paraphrasing the schema. Baseline score of 3 is appropriate.

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

Purpose4/5

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

The description clearly states the tool retrieves logs from multiple resource types (pods, deployments, jobs) and via label selector. It distinguishes from sibling 'get_pod_logs' by mentioning broader resources, but does not explicitly contrast them.

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 is provided on when to use this tool versus alternatives like 'get_pod_logs'. The description lacks context about prerequisites, filtering, or use cases.

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/vijaykodam/kubernetes-readonly-mcp'

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