Skip to main content
Glama

Get ConfigMaps

get_configmaps
Read-only

Fetch ConfigMap summary rows: name, namespace, the data key names, their count and age (never the values). A list needs namespace or all_namespaces=true and carries total, returned, truncated and scope.

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

Input Schema

NameRequiredDescriptionDefault
nameNoSpecific ConfigMap name to fetch.
namespaceNoKubernetes namespace to list. A list needs either this or all_namespaces=true; a named read (name) needs neither.
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
all_namespacesNoSet true to list every namespace on the cluster deliberately. Omit it and pass namespace to list one namespace; a list with neither is refused (error_code scope_required).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds substantive behavior beyond that: values are never returned, the list response carries a total/returned/truncated/scope envelope, and a scoped list is refused. With no output schema, disclosing the envelope is genuinely useful. It stops short of detailing pagination limits or how truncation is signalled beyond the field name.

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?

Two dense sentences, front-loaded with what is returned and followed by the listing precondition. No filler, no restatement of the title.

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 four-parameter read tool with no output schema, the description covers returned fields, the values-suppression guarantee, the required list scope, and the refusal behavior. An agent has everything needed to call it correctly and to know what shape of answer to expect.

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 description coverage is 100%, so all four parameters are already documented, and the description largely restates the namespace/all_namespaces coupling rather than adding new semantics. Baseline 3 applies when the schema does the heavy lifting.

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 and resource ('Fetch ConfigMap summary rows') and enumerates exactly which fields come back (name, namespace, data key names, count, age). The parenthetical '(never the values)' distinguishes it from secret/value-reading siblings like get_secrets, so an agent can pick it without opening any schema.

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?

It gives the scoping rule for a list ('needs namespace or all_namespaces=true') and notes that a named read needs neither, which is real conditional guidance. However, it never says when to prefer this tool over alternatives such as describe_resource, get_secrets, or get_pvcs, so alternative-selection guidance is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.