Skip to main content
Glama

List secrets

list_secrets
Read-only

List the organisation's secrets (secret slots): each one's name, description, how its value was made (created_via: 'user' typed by a person, 'generated' made by Ankra), when it was created and last used, its expiry if it has one, and used_by - the clusters and resources whose definitions carry it. Each comes with its ${SECRET_SLOT:} sentinel, which is what goes into stack values, manifests and MCP server env in place of the value. Values are never returned. These are organisation secrets, not Kubernetes Secrets (get_secrets reads those). Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_secrets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Beyond readOnlyHint=true, it discloses the critical security behavior that values are never returned, and explains the ${SECRET_SLOT:<id>} sentinel and where it is substituted (stack values, manifests, MCP server env). That is meaningful context an agent could not infer from the annotations; only the trailing 'Read-only' restates structured data.

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 purpose and scope, then the returned fields, then the sentinel semantics, then the sibling disambiguation. The field enumeration is dense but each item carries information; only the closing 'Read-only' duplicates the annotation.

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?

There is no output schema, so the description carries the full burden of describing returns — and it does, covering name, description, created_via with value meanings, timestamps, expiry, and used_by. Combined with the sentinel explanation and the Kubernetes-Secret exclusion, nothing an agent needs to select or interpret this call is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so the baseline is 4 and there is nothing for the description to clarify. It correctly omits any parameter discussion rather than inventing one.

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 ('List the organisation's secrets (secret slots)') and immediately defines what a secret slot is. It explicitly names the sibling it is not ('get_secrets reads those' Kubernetes Secrets), so an agent can separate the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context for when this is the right tool and explicitly routes Kubernetes-Secret lookups to get_secrets instead. It stops short of a full when/when-not treatment (e.g. no pointer to request_secret or create_secret for missing slots), but the key disambiguation is present.

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.