Skip to main content
Glama

describe-secret

Retrieve detailed information about a specific Kubernetes secret, including its data and metadata, to inspect configuration or troubleshoot issues.

Instructions

Describe details of a Kubernetes secret

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
secretYesThe name of the secret to describe
namespaceNoThe namespace of the secret (optional, defaults to current context namespace)

Implementation Reference

  • The execution handler for the 'describe-secret' tool. It constructs a 'kubectl describe secret' command using the provided secret name and optional namespace, executes it, and returns the stdout output.
    case "describe-secret": {
      const { secret, namespace } = args;
      const nsArg = namespace ? `-n ${namespace}` : "";
      const cmd = `kubectl describe secret ${secret} ${nsArg}`;
      const { stdout } = await execAsync(cmd);
      return {
        content: [{ type: "text", text: stdout || "No secret details found" }]
      };
    }
  • The tool schema definition including name, description, and input schema for validating arguments: secret (required string), namespace (optional string).
    {
      name: "describe-secret",
      description: "Describe details of a Kubernetes secret",
      inputSchema: {
        type: "object",
        properties: {
          secret: { 
            type: "string",
            description: "The name of the secret to describe"
          },
          namespace: { 
            type: "string",
            description: "The namespace of the secret (optional, defaults to current context namespace)"
          }
        },
        required: ["secret"]
      }
    },
  • server.js:1392-1394 (registration)
    Registration of the describe-secret tool as part of the tools list returned in response to ListToolsRequestSchema.
    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 the full burden of behavioral disclosure. It states the action ('describe details') but doesn't clarify what 'details' include, whether this is a read-only operation, if it requires specific permissions, or what the output format looks like. For a tool accessing sensitive resources like secrets, this is a significant gap.

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 gets straight to the point with zero wasted words. It's appropriately sized for a simple tool and front-loads the essential information.

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

Completeness3/5

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

Given the tool's moderate complexity (accessing sensitive Kubernetes secrets), no annotations, and no output schema, the description is minimally adequate but has clear gaps. It states what the tool does but doesn't address behavioral aspects like safety, permissions, or output format, which are important for this context.

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 the schema already documents both parameters thoroughly. The description doesn't add any additional meaning about parameters beyond what's in the schema, such as format examples or constraints. Baseline 3 is appropriate 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('describe') and resource ('Kubernetes secret'), making the purpose immediately understandable. It distinguishes from siblings like 'get-secret' by specifying 'details' rather than just retrieval, though it doesn't explicitly contrast with them.

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 on when to use this tool versus alternatives like 'get-secret' or 'list-secrets'. The description doesn't mention prerequisites, context, or exclusions, leaving the agent to infer usage from the tool name alone.

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