Skip to main content
Glama

Set application env secret

set_application_env_secret
Destructive

Store the value of one of an Application's environment secrets. The keys come from the Application's own generated manifests - use list_application_env_secrets to see which ones are declared and which are still missing. Storing a value does not reach a running workload: call apply_application_env_secrets to seal the stored values into the Application's deployments and roll them. To clear a value use delete_application_env_secret; an empty string is a value the workload reads as set.

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>",
      "key": "<key>",
      "value": "<value>"
    },
    "name": "set_application_env_secret"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesThe environment variable name, exactly as the manifests spell it.
valueYesThe value to store. It travels inbound only: no route hands a stored value back.
application_idYesThe Application's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations alone only say non-readonly, non-idempotent, destructive. The description adds the non-obvious fact that storing does not affect running workloads until a separate apply/seal-and-roll step, and that stored values are write-only (never returned). That is exactly the operational context an agent cannot infer.

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?

Four short sentences, front-loaded with the core action and then the follow-up chain (list -> set -> apply -> delete). Every sentence carries routing or constraint information; only the closing empty-string clause is slightly tacked on, though it is genuinely useful.

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

Completeness4/5

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

For a three-parameter mutation with no output schema, the description covers prerequisites, side effects, follow-up, and return behavior (nothing returned). The one unaddressed point is overwrite semantics for an existing key, which matters given idempotentHint=false.

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%, so the baseline is 3; the description still adds that keys must come from the Application's generated manifests rather than being arbitrary strings, which meaningfully constrains the 'key' parameter. It does not add further syntax detail, and it repeats the write-only note already present in the schema for 'value'.

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: 'Store the value of one of an Application's environment secrets'. It scopes the operation to per-key secret values, which cleanly separates it from apply_application_env_secrets and delete_application_env_secret.

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?

Explicitly routes the agent: use list_application_env_secrets to discover declared and missing keys, call apply_application_env_secrets to actually reach workloads, and delete_application_env_secret to clear. It also gives an edge-case rule (an empty string is a real value, not a deletion), which prevents the most likely misuse.

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.