Skip to main content
Glama

Environment Variables

environment_variables
Read-onlyIdempotent

List, read, or explain system variables while masking secret-like values; reveal one value only when explicitly requested.

Instructions

List, read or explain environment variables. Secret-like values are masked.

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

Input Schema

NameRequiredDescriptionDefault
nameNoVariable name
valueNoVariable value (set is not supported by the JVM)
actionNolist, get, or set
revealNoReturn secret-like values unmasked for a single get

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior the annotations do not convey: secret-like values are masked by default, which tells the agent to expect redacted output and explains why a reveal path exists. It does not state that mutation is impossible, which the schema's "set" option makes a live question.

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?

Two short sentences, front-loaded with the capability and immediately followed by the most surprising behavior (masking). Nothing is padding and there is no repetition of the title or schema.

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

Completeness3/5

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

For a four-parameter, zero-required tool with no output schema, the masking disclosure is the key thing an agent needs and it is present. What is missing is the relationship between the advertised verbs and the action enum, and the fact that set is unsupported, both of which matter for correct invocation.

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?

Schema description coverage is 100%, so all four parameters are already documented and the baseline is 3. The description only adds the masking rationale behind the reveal flag; it gives no guidance on the action parameter's modes or on what happens when name is omitted.

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?

"List, read or explain environment variables" names a concrete verb set and a concrete resource, so the domain is unambiguous. It loses a point because the third verb ("explain") does not match any value in the schema's action parameter ("list, get, or set"), leaving a small ambiguity about what the tool actually accepts.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus alternatives, no prerequisites, and no exclusions. The only situational hint is the schema-side note that "set is not supported by the JVM" and the description's "for a single get" masking clause, which is not enough to guide tool selection.

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