Skip to main content
Glama
BenedatLLC

Kubernetes Tools MCP Server

by BenedatLLC

get_configmap_summaries

Lists ConfigMap summaries for a namespace or all namespaces, showing name, namespace, key count, data size, and age without reading ConfigMap contents.

Instructions

Retrieves a list of ConfigMapSummary objects for ConfigMaps in a given namespace or all namespaces, similar to kubectl get configmaps.

Note that this returns only summary metadata (not the ConfigMap contents); use
`get_configmap` to read the actual data map.

Parameters
----------
namespace : Optional[str], default=None
    The specific namespace to list ConfigMaps from. If None, lists ConfigMaps from
    all namespaces.

Returns
-------
list of ConfigMapSummary
    A list of ConfigMapSummary objects, each with the following fields:

    name : str
        Name of the ConfigMap.
    namespace : str
        Namespace in which the ConfigMap lives.
    key_count : int
        Number of keys across `data` and `binary_data`.
    data_size : int
        Approximate total size in bytes of all values.
    age : datetime.timedelta
        Age of the ConfigMap (current time minus creation timestamp).

Raises
------
K8sConfigError
    If unable to initialize the K8S API.
K8sApiError
    If the API call to list ConfigMaps fails.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
namespaceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses return fields and specific error cases (K8sConfigError, K8sApiError), which is valuable. However, it does not explicitly state read-only status, side-effect absence, or permission requirements.

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

Conciseness3/5

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

The description is well-structured with headers and front-loads the core purpose. However, the detailed Returns section is largely redundant because an output schema already exists, so some sentences do not earn their place.

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

Completeness5/5

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

For a simple list tool, the description covers purpose, parameter semantics, return summary, and error cases. Nothing essential is missing for an agent to invoke it correctly.

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

Parameters5/5

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

The input schema has 0% description coverage for the single optional 'namespace' parameter. The description fully compensates by explaining its type, default value, and exact semantics (None lists all namespaces).

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?

States a specific verb ('Retrieves') and resource ('ConfigMapSummary objects'), and explicitly distinguishes itself from the sibling get_configmap by noting it returns summary metadata only. The kubectl analogy adds further clarity about scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the alternative tool (get_configmap) for reading actual data and clarifies when to use this one (summary metadata only). It also explains the namespace behavior, leaving no ambiguity about usage context.

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