Skip to main content
Glama

Apply application env secrets

apply_application_env_secrets
Destructive

Seal an Application's stored environment secrets into every deployment of it and roll the workloads that read them. This is the step that makes a stored value reach a running Application: setting a value does not touch what is running until it is applied. It is equally what makes a CLEARED value stop reaching one: an Application whose last key has been deleted applies too, and the apply then REMOVES the sealed Secret from each deployment and rolls the workloads off those values - without it every reconcile puts the deleted values straight back. Takes no values - the ones applied are the ones already stored. It answers a refusal rather than an error when the request does not apply to the Application's current state (not deployed yet, tearing down, a deployment that cannot be sealed, or no Kubernetes Secret Ankra can work out to put the values in), and the refusal says which. An empty catalogue is NOT a refusal.

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": "apply_application_env_secrets"
  }
}

Input Schema

NameRequiredDescriptionDefault
application_idYesThe Application's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already flag destructiveHint=true and idempotentHint=false, but the description adds substantial context beyond them: workload rolling, removal of the sealed Secret when the last key is deleted, that no values are accepted as input, and that inapplicable state produces a refusal rather than an error. It does not describe the response payload, but the destructive and refusal semantics are unusually well covered.

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

Conciseness3/5

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

The core purpose is front-loaded, but the description runs long and uses capitalized emphasis, and the cleared-value scenario is explained at length. Each part is relevant, yet the same point (apply is required for state to reach workloads) is restated more than once.

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 and only one parameter, so the description has to carry the state and failure semantics, which it does. Refusal conditions, the empty-catalogue case, and the destructive removal path are all covered, leaving no significant gap for calling the tool correctly.

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?

Schema coverage is 100% for the single application_id parameter, so the baseline is already high. The description still adds real meaning by stating that the tool takes no values and applies only what is already stored, which prevents an agent from trying to pass secret contents.

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?

The description gives a specific verb and resource: it seals stored environment secrets into every deployment and rolls the workloads that read them. It also draws the exact line against the sibling set_application_env_secret by saying that setting a value does not touch what is running until it is applied.

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

Usage Guidelines5/5

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

It explicitly states when to use it, after a value is set or cleared, and why skipping it fails (every reconcile restores deleted values). It also names the state conditions under which the tool refuses, so the agent knows when not to expect success.

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.