Skip to main content
Glama

List Environments

environments_list
Read-only

Lists an app's deploy-plane environments (development/staging/ production): each environment's environment_id, type, region, base_url, healthcheck_path, Cloud Run scaling configuration (cpu, memory, min_instances, max_instances, concurrency, timeout_seconds), config_pending_deploy (true when settings changed that only reach the app with the next deploy) with config_changed_at, database_status, and when the managed database failed to provision, sanitised database_error_code / database_error_message. Takes the app_id returned by apps_list. Use the returned environment_id with deployments_list, logs_tail, or deployment_create.

base_url is where the environment answers once deployed (the same as public_url), null until the first runtime deploy. public_url is https:// + platform_hostname, the Meridian hostname. domains lists the platform domain (kind: "platform", status active, not_deployed or disabled while hosting is off), then each custom domain (kind: "custom") with its status (pending_dns, provisioning, active, failed, deleting), certificate state tls (active, provisioning, failed, or null when Meridian holds none), dns_all_verified, the dns_records to add, certificate_expires_at, ownership_expires_at and error_message.

database is the environment's database (status, engine, error_code, error_message), or null when it has none: the database add-on when there is one, else the legacy managed database. database_status is its status: pending, provisioning, ready, failed, deleting or deleted. Never a host, user, database name or password.

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>"
    },
    "name": "environments_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idYesThe app uuid returned by `apps_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
Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), yet the description adds substantial behavior: `base_url` is null until the first runtime deploy, `config_pending_deploy`/`config_changed_at` semantics, database status state machine (pending/provisioning/ready/failed/deleting/deleted), and the explicit security guarantee that no host, user, database name, or password is ever returned.

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?

Purpose is front-loaded in the first sentence and the return-field detail earns most of its space because no output schema exists. It is nonetheless a dense, backtick-heavy wall of prose whose domain/base-url/database paragraphs could be tighter and better segmented.

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 carries the full burden of explaining return values and does so thoroughly: environment fields, scaling config, `base_url` vs `public_url`, domain kinds and statuses, TLS state, and database status semantics. Nothing essential for correct interpretation is missing.

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% and both parameters are documented there, including the `organization_id` slug-resolution behavior that the description never mentions. The description only restates that `app_id` comes from `apps_list`, so it adds no meaning beyond the schema; the baseline of 3 applies.

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?

Opens with a specific verb and resource plus scope: 'Lists an app's deploy-plane environments (development/staging/production)'. It also names the upstream source of the input (`app_id` returned by `apps_list`) and the downstream consumers (`deployments_list`, `logs_tail`, `deployment_create`), so an agent can place it precisely among siblings.

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?

Clear workflow context: obtain `app_id` from `apps_list`, then reuse the returned `environment_id` in `deployments_list`, `logs_tail`, or `deployment_create`. There is no explicit 'use X instead when…' exclusion or precondition for the `organization_id` variant, so it stops short of full routing guidance.

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