Skip to main content
Glama
Sign In
Kubernetes MCP Server

Kubernetes MCP Server

by Portfolio-jaime
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_cluster_info

Retrieve overall Kubernetes cluster health and configuration details, including nodes, namespaces, and resource availability, to quickly assess cluster status.

Instructions

Obtener información general del cluster

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_cluster_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It implies a read-only operation via 'Obtener,' but it does not explain the return structure, potential sizes, or any operational caveats. The description essentially restates the tool name without adding meaningful behavioral detail.

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 short sentence with no filler or redundant elaboration. It is front-loaded, though the word 'general' is imprecise and reduces clarity without adding much value.

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?

There is no output schema and no annotation context, yet the description does not specify what 'general cluster information' includes. An agent cannot tell whether this returns node status, resource usage, versions, or something else, making the definition incomplete for correct use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters and the input schema is empty, so schema coverage is trivially 100%. With no parameters, there is nothing the description must clarify; the baseline of 4 applies.

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: 'obtener información general del cluster' (get general cluster information). It broadly distinguishes the tool from resource-specific siblings like get_pods and get_helm_releases, though 'general information' remains vague about what exactly is returned.

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 about when to use this tool versus alternatives such as get_pods or get_outdated_components. There are no exclusions, prerequisites, or context clues beyond the generic phrase 'general cluster info.'

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