Skip to main content
Glama
Sign In
KubeCraft MCP Server

KubeCraft MCP Server

by cloudcrafttech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Diagnose Pod

diagnose_pod

Retrieve comprehensive pod diagnosis including status, conditions, container states, events, and recent logs in one API call.

Instructions

Comprehensive pod diagnosis: status, conditions, container states, events, and recent logs in one call.

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

Input Schema

NameRequiredDescriptionDefault
nameYesPod name
namespaceNoNamespace (default: 'default')default

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the types of data returned but does not mention potential permissions, rate limits, or side effects. It is adequate but not exhaustive.

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, highly efficient, front-loaded with the key term 'comprehensive'. 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?

Given no output schema, the description usefully lists the components returned (status, conditions, container states, events, logs). Lacks details on pagination or error handling, but sufficient for a diagnostic tool.

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 parameters are explained in the schema. The description adds no additional meaning beyond what is already in the parameter descriptions.

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 tool performs comprehensive pod diagnosis, listing specific aspects like status, conditions, container states, events, and logs. This effectively distinguishes it from sibling tools such as get_pod_logs and get_events.

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 when to use this tool (for a full overview) but does not explicitly state when not to use it or provide alternatives. Given numerous sibling tools, more explicit guidance would be helpful.

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