Skip to main content
Glama
mcp-airlock

mcp-airlock

by sigma5667

Print Environment Tool

get-env
Read-onlyIdempotent

Returns environment variables to debug MCP server configuration while masking credential-like values unless secrets are explicitly enabled.

Instructions

Returns all environment variables, helpful for debugging MCP server configuration. Values of credential-like names (a KEY, TOKEN, SECRET, PASSWORD, PASSWD, CREDENTIAL, AUTH or COOKIE name segment) are masked as "" unless GET_ENV_INCLUDE_SECRETS is set to 1 or true in the server's environment.

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": "get-env"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

The annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world). Beyond that, the description discloses a non-obvious behavioral trait an agent could not infer: credential-like values are replaced with "<redacted>", and it defines exactly which name segments trigger masking and how to disable it via GET_ENV_INCLUDE_SECRETS. That is the kind of context annotations cannot carry and directly prevents misinterpretation of the output.

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?

Two sentences with the core behavior front-loaded, and no filler. The parenthetical enumeration of masked name segments is long but each entry adds precision about what gets redacted. Slightly denser than necessary, but every clause earns its place.

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 burden of explaining what comes back, and it does: all environment variables, with credential-like values masked. Combined with a no-parameter schema and full annotation coverage, an agent has everything needed to call it and interpret the result safely.

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?

With zero parameters, the baseline is 4, and this description meets it while adding a useful note about a server-environment control (GET_ENV_INCLUDE_SECRETS) that affects the result even though it is not an input parameter. It does not elaborate on the return structure (for example, a name/value mapping), but no parameter meaning is left ambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: "Returns all environment variables." That is unambiguous and clearly distinct from sibling readers such as get-header-params or get-resource-links. It does not explicitly name a sibling or state what it is not, which keeps it just short of a 5.

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?

"helpful for debugging MCP server configuration" gives a concrete use context, so an agent knows when to reach for this rather than other read tools. It stops short of explicit exclusions or prerequisites (for example, that the output may be noisy or that secrets are hidden by default unless a server-side flag is set).

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