Skip to main content
Glama

env

Idempotent

Environment variables, secrets, config and integration keys. It sets with project_id, key and value; deletes with key and delete:true; lists with project_id only. Values are encrypted and omitted from list results. New values are private for server functions by default. A VITE_ or REACT_APP_ prefix alone never publishes a value. Publishing a browser value requires a prefixed name and public:true. Recognized secret credentials, including test credentials, cannot be marked public. Server functions read sw.env.NAME. Browser code reads import.meta.env.VITE_NAME or process.env.REACT_APP_NAME only for explicitly public values. A private browser reference refuses compilation. Provider and purpose are optional descriptive labels, not access controls. After the project adopts live config on a deploy, saves reach new ordinary requests within 60 seconds, usually in a few seconds. Cron and new background deliveries see changes within 5 seconds. Public browser values reach new page loads within 60 seconds. Previews keep the config they captured. List and save responses contain exact references and effective visibility, never values. A project's combined environment values have a 5,120 byte limit.

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

Input Schema

NameRequiredDescriptionDefault
keyNoVariable name, e.g. "STRIPE_SECRET_KEY"
scopeNoOptional scope. 'all' (default) applies to live and any enabled preview. 'prod' restricts the value to live. 'dev' requires hosted preview access for signed-in accounts on every plan.
valueNoVariable value (will be encrypted). Required when setting.
deleteNotrue deletes the variable specified by key.
publicNoExplicit browser visibility. New values default private; omitted on rotation preserves current visibility. Requires a VITE_/REACT_APP_ name. Recognized credentials cannot be public.
purposeNoOptional non-secret description (max 240 characters). Omitted: retained; empty string clears.
providerNoOptional non-secret integration label (max 64 characters). Omitted: retained; empty string clears.
project_idYesProject ID (UUID), subdomain, or slug — resolved server-side, no UUID lookup needed. 'default' also works when the account has exactly one project; multi-project accounts must name one (the error lists them).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / public / description
      Previous value: -"Explicit browser visibility. New values default private; omitted on rotation preserves current visibility. Requires a VITE_/REACT_APP_ name and redeploy to appear in browser code. Recognized credentials cannot be public."New value: +"Explicit browser visibility. New values default private; omitted on rotation preserves current visibility. Requires a VITE_/REACT_APP_ name. Recognized credentials cannot be public."
  2. First observed

TDQS

A3.5/5.0
Behavior1/5

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

The annotations declare destructiveHint:false, but the description explicitly states the tool 'deletes with key and delete:true', which is a destructive operation. Under the scoring rule this is an annotation contradiction, so behavioral transparency is scored 1 despite the description otherwise disclosing rich behavior such as encryption, visibility, propagation timing, and the 5,120-byte limit.

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?

It front-loads the resource and operation summary, then provides necessary policy details with no obvious filler. The result is a dense multi-sentence paragraph; the length is largely earned by the tool's complexity, but the structure could be easier to scan.

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?

It covers operations, encryption and visibility rules, server/browser read syntax, propagation timing, preview behavior, response contents, and the combined 5,120-byte limit. With no output schema, it still explains what list and save responses contain, making it complete for this complexity.

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 description coverage is 100% and already documents all eight parameters. The description still adds value by clarifying operation composition and stating that provider and purpose are optional descriptive labels, not access controls, but it does not add deep syntax beyond the schema.

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 'Environment variables, secrets, config and integration keys' and enumerates set, delete, and list operations, making the resource and actions clear. It does not explicitly differentiate this tool from any sibling tool, so it stops 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?

It gives operation-level guidance: set with project_id, key, and value; delete with key and delete:true; list with project_id only. It also explains public/private usage rules, but it does not name when-not scenarios or alternative tools, so 4 rather than 5.

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