Skip to main content
Glama
Sign In
k8scortex-mcp

k8scortex-mcp

by apatilgtn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

describe_pod

Get detailed Kubernetes pod status including container states, conditions, resource settings, and recent events.

Instructions

Shows detailed pod status including container states, conditions, resource settings, and recent events.

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": {
      "namespace": "<namespace>",
      "podName": "<podName>"
    },
    "name": "describe_pod"
  }
}

Input Schema

NameRequiredDescriptionDefault
clusterNoTarget cluster name (default: 'default')
podNameYesThe name of the pod
namespaceYesThe Kubernetes namespace

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose traits. It identifies output aspects but does not mention read-only nature, required permissions, or any side effects. Adequate for a describe tool but could be more explicit.

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, front-loaded sentence with no wasted words. Every word adds value.

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?

Given the tool's simplicity and no output schema, the description covers the main aspects of pod status. It could mention return format, but the listed details suffice for understanding.

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 does not add meaning beyond the schema; it only states the overall purpose without connecting to 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?

The description clearly states the verb 'Shows' and the resource 'detailed pod status', and lists specific details (container states, conditions, resource settings, events). It distinguishes from sibling tools like list_pods (which only lists) and get_pod_logs (which retrieves logs).

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 over siblings (e.g., list_pods, describe_deployment). No context on prerequisites or scenarios where it is the best choice.

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

Deploy Server

Other Tools