Skip to main content
Glama
Sign In
mcp-server-kubernetes

mcp-server-kubernetes

by ACRT-EVAL
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_deployments

Lists all deployments in a specified Kubernetes namespace to help you inspect running workloads and manage cluster resources.

Instructions

List deployments in a namespace

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

Input Schema

NameRequiredDescriptionDefault
namespaceYesdefault

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read-only list operation but does not disclose permissions, pagination, ordering, or output behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no wasted wording. It is concise, though it is terse to the point of omitting useful context.

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

Completeness2/5

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

The tool is simple, but there are no annotations, no output schema, and no parameter descriptions. The description does not explain what a returned deployment looks like or how listing behaves, leaving significant gaps for an agent.

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?

The schema description coverage is 0%, so the description should compensate for the single namespace parameter. It mentions namespace scope but does not explain namespace format, the default value, or what happens when it is omitted.

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 states a clear verb and resource: list deployments, scoped to a namespace. This is more specific than the name alone, but it does not explicitly differentiate from siblings such as list_pods, list_services, or create_deployment beyond the obvious resource noun.

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?

It says where deployments are listed but gives no guidance on when to use this tool versus alternatives like describe_pod, list_services, or create_deployment. There are no exclusions, prerequisites, or alternative-selection criteria.

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