Skip to main content
Glama

List application env secrets

list_application_env_secrets
Read-only

Read the environment secrets an Application's generated manifests declare: every key, whether it has a value yet, which keys are still missing, the Kubernetes Secrets the deploy renders them into (secret_names - a monorepo's components each read one named after themselves, so there can be more than one), and whether what is RUNNING already carries the current values (apply_state: applied, pending, unknown, or not_deployed). Read requirements_state BEFORE missing_keys: an empty missing_keys means 'nothing is missing' only under 'known'. Under 'unknown' Ankra could not establish what the Application needs - no manifest is recorded yet, or the manifests read an env Secret it does not fill (unfilled_secrets names it) - and neither missing_keys nor any key's required flag is a claim about the Application, so do not report it as fully configured. This is the read to reach for when a deployed Application crashes on startup or reports missing configuration - a key with no value, or an apply_state of 'pending', explains it. A secret's value is never returned by this or any other route: secrets are reported by key and state only. The Application's shared plain values (configuration that is not a credential, sealed into the same Secret) are listed in plain_values with their values, and a key a plain value fills is set, not missing; plain_values is null when they could not be read, and plain_values_unreadable says why - never report that as the Application having none. Read-only.

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": {
      "application_id": "<application_id>"
    },
    "name": "list_application_env_secrets"
  }
}

Input Schema

NameRequiredDescriptionDefault
application_idYesThe Application's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, and the description adds substantial behavioral context beyond that: the meaning of each apply_state value, the caveat that an empty missing_keys only means 'nothing is missing' under 'known', the unfilled_secrets case, and that missing_keys/required flags are not claims under 'unknown'. It also discloses the null-vs-empty distinction for plain_values and plain_values_unreadable, which prevents a real misreporting error.

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?

Dense but front-loaded: the read verb and resource come first, then returned fields, then the crash-diagnosis use case, then the value-redaction caveat. Almost every sentence carries semantics, though it is one long unbroken paragraph and the ordering constraint about requirements_state would be easier to act on if segmented.

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 must carry the return contract, and it does: it names each field's meaning, the four apply_state values, the known/unknown requirements_state branches, secret_names plurality in monorepos, and the plain_values null case. Nothing an agent needs to interpret the response correctly appears to be missing.

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?

There is a single parameter (application_id) at 100% schema description coverage, so the schema already carries the parameter's meaning. The description adds no extra syntax, format, or sourcing detail for application_id, so the baseline of 3 applies.

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?

Opens with a specific verb+resource and a precise scope: 'Read the environment secrets an Application's generated manifests declare.' It then enumerates exactly what is returned (keys, missing_keys, secret_names, apply_state, requirements_state), which separates it from the generic secret routes, and explicitly notes secret values are never returned 'by this or any other route' — closing the ambiguity an agent might have with list_secrets/get_secrets.

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 a clear triggering scenario: 'reach for when a deployed Application crashes on startup or reports missing configuration.' It also prescribes an internal read order ('Read requirements_state BEFORE missing_keys'), which is genuine usage guidance. It stops short of naming an alternative tool or stating when not to use it, so it is not a 5.

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.