Skip to main content
Glama

Get secrets

get_secrets
Read-only

Fetch Secret metadata. Returns: name, namespace, type, the list of data key names (NOT their decoded values), data key count, age, and for service-account token secrets only the bound ServiceAccount and a boolean indicating whether the token field is populated. Decoded secret values are never returned. 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_secrets"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoSpecific Secret name to fetch metadata for.
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/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses the exact return shape (name, namespace, type, data key names, key count, age), the service-account token special case, and the security-relevant guarantee that decoded values are never returned. It also documents list metadata (total, returned, truncated, scope), which is substantial behavioral context.

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

Conciseness4/5

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

Front-loaded with the core action and the no-decoded-values guarantee, then the return fields, then the list scoping rule. Dense but every sentence carries information; the return-field enumeration is long but justified given there is no output schema.

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?

With no output schema, the description fully compensates by enumerating return fields, the token special case, and list truncation metadata. Combined with the schema's parameter documentation, an agent has everything needed to call it correctly.

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%, so all four parameters are already documented, including the scope_required error for a list with neither namespace nor all_namespaces. The description restates the list-vs-named-read rule but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Fetch Secret metadata') and immediately bounds the scope by declaring that decoded values are never returned. It is clear what the tool does, but it never names the sibling list_secrets, so an agent must infer the boundary between the two overlapping tools.

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?

The description explains the scoping rule for a list (namespace or all_namespaces=true) and that a named read needs neither, which is useful invocation guidance. However, it gives no explicit when-to-use versus list_secrets or create_secret/request_secret, leaving the sibling choice to inference.

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.