Skip to main content
Glama

get_secret_for_env

Reveals a stored secret value by name for child processes that must read it from an environment variable; always requires approval and returns only secrets from configured presets or wrapped servers.

Instructions

Reveal the raw secret value bound to a name. ALWAYS prompts for approval, regardless of preset policy. Prefer proxy_http — only use this if a child process you are about to spawn must read the secret from an environment variable (e.g. terraform apply reading AWS_SECRET_ACCESS_KEY). Only the secret of a configured preset or wrapped server can be revealed. The returned value MUST NOT be quoted back into your reasoning trace.

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

Input Schema

NameRequiredDescriptionDefault
nameYesName of the secret to reveal.

Output Schema

NameRequiredDescriptionDefault
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full disclosure burden, and it does well: it flags that approval is always prompted regardless of preset policy, and that the returned value must not be quoted into the reasoning trace. It does not describe output shape or whether the value is cached, though the presence of an output schema reduces the need to. The unqualified claim about prompting behavior is context the agent would otherwise have to discover by trial.

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

Conciseness5/5

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

Four short sentences, front-loaded with what the tool does, then the safety override, then eligibility, then handling. Every sentence adds a distinct constraint; nothing is redundant with the title or 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?

For a one-parameter secret-reveal tool with an output schema and no annotations, the description covers the missing pieces an agent needs: the approval gate, the preferred alternative, the eligibility restriction, and post-call handling of the returned value. Return-value semantics are legitimately deferred to the output schema.

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% and the single `name` param is documented, so the baseline is solid. The description adds meaning beyond the schema by constraining which names are valid: only secrets belonging to a configured preset or wrapped server, which the schema's terse 'Name of the secret to reveal' does not convey.

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?

A specific verb and resource: 'Reveal the raw secret value bound to a name.' It immediately distinguishes itself from the sibling `proxy_http`, which it names directly, so an agent knows this is the raw-extraction path rather than the mediated-request path.

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 states the preferred alternative (`proxy_http`) and the narrow condition that overrides that preference: a child process about to be spawned must read the value from an environment variable, with a concrete example (`terraform apply` reading AWS_SECRET_ACCESS_KEY). It also names a hard eligibility limit — only secrets of a configured preset or wrapped server can be revealed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.