k8scortex-mcp

get_configmap

Retrieves data from a Kubernetes ConfigMap. Provide namespace and ConfigMap name to access its configuration values.

Instructions

Reads data from a ConfigMap.

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

Input Schema

Name	Required	Description
`cluster`	No	Target cluster name (default: 'default')
`namespace`	Yes	The Kubernetes namespace
`configMapName`	Yes	The name of the ConfigMap

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Jul 28, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It states 'Reads data' implying a non-destructive read, but does not specify what exactly is returned, authorization needs, or error behavior.

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?

The description is a single, concise sentence that is front-loaded and contains no unnecessary words. It is appropriately sized for a simple read operation.

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?

Given the lack of an output schema and the simplicity of the tool, the description should at least hint at the return format (e.g., 'returns the ConfigMap data as a map of key-value pairs'). It fails to do so, leaving a gap in completeness.

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%, and all parameters (cluster, namespace, configMapName) have descriptions. The description adds no extra meaning beyond the schema, warranting a baseline score of 3.

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 'Reads data from a ConfigMap' clearly states the verb and resource, distinguishing it from sibling tools like create_configmap and update_configmap. It is not a tautology and provides specific purpose.

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 given on when to use this tool versus alternatives. The description does not mention prerequisites, when not to use, or suggest alternative tools for listing or modifying ConfigMaps.

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

Deploy Server