Skip to main content
Glama

List environment variables

list_env_vars
Read-onlyIdempotent

List the environment variables an app or agent receives: each one's name, whether it is a secret, its scope (service for its own, org for one it inherits), and whether a service variable overrides an org one. A plain variable's value is shown; a secret's value never is. Organization variables are listed here but are changed from the dashboard or CLI, not by these tools. Requires connecting a Valet account.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe app's or agent's name, as list_services shows it: the one whose variables to list.
org_nameNoThe Valet organization it belongs to. Omit to use the organization the account joined first.

Output Schema

NameRequiredDescriptionDefault
orgYesName of the Valet organization the call acted in.
nameYesName of the app or agent the variables are listed for.
varsYesThe variables the app or agent receives: its own and those inherited from the organization. Empty when there are none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"The app's or agent's name."New value: +"The app's or agent's name, as list_services shows it: the one whose variables to list."
  2. Changed9 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"Required. The service's name."New value: +"The app's or agent's name."
    • addedOutput schema / properties / name / description
      Added value: +"Name of the app or agent the variables are listed for."
    • addedOutput schema / properties / org / description
      Added value: +"Name of the Valet organization the call acted in."
    • addedOutput schema / properties / vars / description
      Added value: +"The variables the app or agent receives: its own and those inherited from the organization. Empty when there are none."
    • addedOutput schema / properties / vars / items / properties / name / description
      Added value: +"Variable name."
    • addedOutput schema / properties / vars / items / properties / overrides_org / description
      Added value: +"True when this service variable replaces an organization variable of the same name. Always false for an org-scoped variable."
    • addedOutput schema / properties / vars / items / properties / scope / description
      Added value: +"service when set on this app or agent, org when inherited from the organization. Change org variables from the dashboard or CLI."
    • addedOutput schema / properties / vars / items / properties / secret / description
      Added value: +"True for a secret, whose value is never shown. False for a plain variable."
    • addedOutput schema / properties / vars / items / properties / value / description
      Added value: +"The value of a plain variable. Absent for a secret, and for a plain variable with an empty value."
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "name": {
      +      "type": "string"
      +    },
      +    "org": {
      +      "type": "string"
      +    },
      +    "vars": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "name": {
      +            "type": "string"
      +          },
      +          "overrides_org": {
      +            "type": "boolean"
      +          },
      +          "scope": {
      +            "type": "string"
      +          },
      +          "secret": {
      +            "type": "boolean"
      +          },
      +          "value": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "name",
      +          "secret",
      +          "scope",
      +          "overrides_org"
      +        ],
      +        "type": "object"
      +      },
      +      "type": [
      +        "null",
      +        "array"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "org",
      +    "name",
      +    "vars"
      +  ],
      +  "type": "object"
      +}
  4. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive behavior, and the description adds real substance beyond them: secret values are never exposed while plain values are shown, and each entry is tagged with scope and override status. It also discloses the authentication prerequisite, though it says nothing about pagination or volume limits.

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?

The definition is front-loaded with the core action and then layers the secrecy and scope semantics in a single dense sentence. Every clause carries information; the only cost is that the middle sentence packs several concepts together, slightly reducing skimmability.

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?

An output schema exists, so return-value explanation is not required, yet the description still characterizes the payload (name, secret flag, scope, override flag, value visibility). Combined with the auth prerequisite and scope rules, an agent has everything needed to call this correctly.

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 coverage is 100%, with the name and org_name parameters already well documented, so the baseline applies. The description's scope discussion (service variable for its own, org for one it inherits) adds incidental meaning about what org_name resolves to, but it does not directly describe parameter formats or the default-org fallback beyond what the schema states.

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 ("List the environment variables an app or agent receives") and enumerates the fields returned, so an agent knows exactly what it gets back. It does not name the mutating siblings (set_env_vars/unset_env_vars) by name, only referring obliquely to "these tools," so differentiation is implied rather than explicit.

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

Usage Guidelines3/5

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

Useful context is given: organization variables are listed here but changed elsewhere (dashboard or CLI), and a Valet account connection is required. However, there is no explicit instruction to use set_env_vars or unset_env_vars for modifications, so routing to the correct sibling is left to inference.

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.

Resources