Skip to main content
Glama

List Managed Environment Variables

managed_variables_list
Read-only

Lists the environment variables Meridian itself injects into an environment's runtime at deploy time: SHOPIFY_API_KEY, SHOPIFY_API_SECRET, SHOPIFY_APP_URL (the environment's Meridian address), the MERIDIAN_* platform identifiers, and the managed database DB_* set. These are NOT in the app's repository and NOT returned by secrets_list, but they are readable from the process environment at runtime, so read this before writing code that reads a variable or before adding one the platform already provides.

Each entry has name, secret (true when the value is mounted from Secret Manager), source (sdk_credentials, platform or database), and the two directions a name collision with a declared variable can resolve in: overridden: the app's own variable wins and the injected one is skipped; shadows_user_variable: this one is injected unconditionally and the app's variable of that name never reaches the runtime, so setting it has no effect (the MERIDIAN_* identifiers). override_value says, for an overridden entry, whether the app's variable holds the same value as the managed one (same, different, or unknown when the values cannot be compared), and is null when nothing overrides the entry. Only the Shopify pair and NODE_ENV are compared, reading two secrets at most, the Shopify pair first. Remove an override with secrets_unset.

VALUES ARE NEVER RETURNED, for managed or declared variables alike; read them in the Meridian dashboard. Only variables whose injection conditions currently hold are listed, so an environment with no database reports no DB_* entries.

Takes the app_id from apps_list and the environment_id from environments_list.

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": {
      "app_id": "<app_id>",
      "environment_id": "<environment_id>"
    },
    "name": "managed_variables_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idYesThe app uuid returned by `apps_list`.
environment_idYesThe environment to inspect, from `environments_list`.
organization_idNoAn organisation uuid or slug. When supplied, `app_id` is resolved within that organisation and may be a slug instead of a uuid, mirroring the Meridian web app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare a safe read; the description adds substantial behavior on its own — values are never returned, only variables whose injection conditions currently hold are listed (no DB_* without a database), and the override comparison is bounded to the Shopify pair and NODE_ENV, reading at most two secrets. The collision-resolution semantics (`overridden` vs `shadows_user_variable`) are spelled out, which no annotation or schema conveys.

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?

Front-loaded with what the tool returns and what it is not, then per-field semantics, then the critical 'values are never returned' constraint. It is dense and long, and the sentence about which pairs are compared and in what order could be trimmed, but nearly every clause carries operational meaning.

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?

With no output schema, the description takes on the burden of explaining the return record and does so completely: `name`, `secret`, `source` with its enum values, `overridden`, `shadows_user_variable`, and `override_value` with its states. For a read-only list tool of this complexity, an agent has everything needed to interpret results 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%, so both required parameters are already documented, and the description mainly repeats that linkage (app_id from `apps_list`, environment_id from `environments_list`). It says nothing about `organization_id`, whose slug-resolution behavior lives only in the schema, so it adds little meaning beyond structured data.

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?

States a specific verb and resource (lists Meridian-injected environment variables for an environment) and enumerates the concrete families returned (SHOPIFY_*, MERIDIAN_*, DB_*, NODE_ENV). It explicitly distinguishes itself from the nearest sibling: these are NOT returned by `secrets_list`.

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?

Gives explicit when-to-use guidance: read this before writing code that reads a variable, or before adding one the platform already provides. It also routes the agent to the right siblings for adjacent jobs — `secrets_list` for declared secrets, `secrets_unset` to remove an override, `apps_list`/`environments_list` for the ids.

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