Skip to main content
Glama

label

Add or update labels on Kubernetes resources to organize, select, and manage cluster objects using key-value pairs.

Instructions

Add or update labels on a resource

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
resourceYesThe resource type
nameYesThe name of the resource
labelsYesLabels to add/update (key=value,key2=value2)
namespaceNoThe namespace of the resource (optional, defaults to current context namespace)

Implementation Reference

  • Handler function for the 'label' tool that destructures arguments, constructs a 'kubectl label' command, executes it via execAsync, and returns the stdout or a success message.
    case "label": {
      const { resource, name, labels, namespace } = args;
      const nsArg = namespace ? `-n ${namespace}` : "";
      const cmd = `kubectl label ${resource} ${name} ${labels} ${nsArg}`;
      const { stdout } = await execAsync(cmd);
      return {
        content: [{ type: "text", text: stdout || `Labels updated on ${resource} ${name}` }]
      };
    }
  • Tool schema definition for 'label', including name, description, and inputSchema with properties for resource, name, labels (required), and optional namespace.
      name: "label",
      description: "Add or update labels on a resource",
      inputSchema: {
        type: "object",
        properties: {
          resource: { 
            type: "string",
            description: "The resource type"
          },
          name: { 
            type: "string",
            description: "The name of the resource"
          },
          labels: { 
            type: "string",
            description: "Labels to add/update (key=value,key2=value2)"
          },
          namespace: { 
            type: "string",
            description: "The namespace of the resource (optional, defaults to current context namespace)"
          }
        },
        required: ["resource", "name", "labels"]
      }
    },
  • server.js:1391-1394 (registration)
    Registration of the tool list handler that returns the array of all tools (including 'label') in response to ListToolsRequestSchema.
    // Handle tool listing
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a mutation operation ('Add or update'), but doesn't clarify whether this overwrites existing labels, merges with them, or requires specific permissions. No information about rate limits, side effects, or error conditions is provided, leaving significant behavioral gaps.

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, efficient sentence that communicates the core functionality without unnecessary words. It's front-loaded with the essential action and target. Every word earns its place, making this an excellent example of conciseness in tool descriptions.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens when labels are added/updated, whether the operation is idempotent, what permissions are required, or what the response looks like. Given the complexity of modifying Kubernetes resources, more contextual information is needed for safe and effective use.

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 parameters are documented in the schema. The description adds no additional parameter semantics beyond what's already in the schema descriptions. It doesn't explain the format of 'labels' beyond the schema's 'key=value,key2=value2' or provide examples of valid 'resource' types. This meets the baseline for high schema coverage.

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 clearly states the action ('Add or update') and target ('labels on a resource'), making the purpose immediately understandable. It distinguishes itself from siblings like 'annotate' by focusing specifically on labels rather than general annotations. However, it doesn't specify what types of resources can be labeled, which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives like 'annotate' or 'patch'. It doesn't mention prerequisites, permissions needed, or typical use cases. The agent must infer usage from the tool name and parameters alone, which is insufficient for optimal decision-making.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/thekaranpargaie/kube-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server