Opsphere — DevOps & SRE Intelligence

Vercel Env List

vercel_env_list

Read-only

List env vars from the Vercel API (no local infra repo required). Use keys + includeValues:true to read decrypted config values from Vercel; Secret-type vars stay write-only per Vercel. Values omitted by default. The param is "project" (NOT "projectName"). There is NO separate "environment" param — the env is part of the project name/alias. Example: {project:"your-tenant-storefront-prod"}. Accepts brand aliases: "your-tenant-int" → "your-tenant-storefront-int", "your-tenant-tst" → "your-tenant-storefront-tst". Also accepts prd/prod, stg/pre, test/tst.

Input Schema

Name	Required	Description	Default
`keys`	No	Return only these env keys (case-sensitive)
`redact`	No	Redact sensitive values in output when includeValues is true	secrets
`teamId`	No	Team ID if applicable
`decrypt`	No	Deprecated alias for includeValues
`project`	Yes	Project name, ID (prj_xxx), or brand alias from catalog. The environment is embedded in the name (e.g. your-tenant-tst, your-tenant-prd). Do NOT pass a separate environment param
`context_id`	No	Optional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.
`includeValues`	No	Fetch decrypted values when Vercel allows (config vars)

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	Yes
`contractVersion`	Yes
`dataSchemaVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedOct 26, 2026

changedOutput schema / properties / data / additionalProperties
```
Previous value: -trueNew value: +false
```
removedOutput schema / properties / data / properties / count
```
Removed value: -{
-  "type": "number"
-}
```

removedOutput schema / properties / data / properties / deployments

Removed value: -{
-  "items": {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  "type": "array"
-}

removedOutput schema / properties / data / properties / envs

Removed value: -{
-  "$ref": "#/properties/data/properties/deployments"
-}

addedOutput schema / properties / data / properties / family

Added value: +{
+  "const": "vercel",
+  "type": "string"
+}

addedOutput schema / properties / data / properties / gaps

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

removedOutput schema / properties / data / properties / items

Removed value: -{
-  "$ref": "#/properties/data/properties/deployments"
-}

addedOutput schema / properties / data / properties / operation

Added value: +{
+  "const": "vercel_env_list",
+  "type": "string"
+}

addedOutput schema / properties / data / properties / partial
```
Added value: +{
+  "type": "boolean"
+}
```

removedOutput schema / properties / data / properties / project

Removed value: -{
-  "$ref": "#/properties/data/properties/deployments/items"
-}

removedOutput schema / properties / data / properties / projects

Removed value: -{
-  "$ref": "#/properties/data/properties/deployments"
-}

addedOutput schema / properties / data / properties / records

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "branch": {
+        "type": "string"
+      },
+      "createdAt": {
+        "type": "string"
+      },
+      "durationMs": {
+        "type": "number"
+      },
+      "environment": {
+        "type": "string"
+      },
+      "facts": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "name": {
+              "type": "string"
+            },
+            "value": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "number"
+                },
+                {
+                  "type": "boolean"
+                },
+                {
+                  "type": "null"
+                },
+                {
+                  "items": {
+                    "type": [
+                      "string",
+                      "number",
+                      "boolean",
+                      "null"
+                    ]
+                  },
+                  "type": "array"
+                }
+              ]
+            }
+          },
+          "required": [
+            "name",
+            "value"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "id": {
+        "type": "string"
+      },
+      "key": {
+        "type": "string"
+      },
+      "message": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "project": {
+        "type": "string"
+      },
+      "region": {
+        "type": "string"
+      },
+      "revision": {
+        "type": "string"
+      },
+      "service": {
+        "type": "string"
+      },
+      "status": {
+        "type": "string"
+      },
+      "summary": {
+        "type": "string"
+      },
+      "tags": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "title": {
+        "type": "string"
+      },
+      "type": {
+        "type": "string"
+      },
+      "updatedAt": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "facts"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / data / properties / summary
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / data / properties / total

Added value: +{
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / data / properties / truncated
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / data / properties / warnings

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / data / required

Added value: +[
+  "family",
+  "operation",
+  "records",
+  "total",
+  "partial",
+  "truncated",
+  "warnings",
+  "gaps"
+]

addedOutput schema / properties / dataSchemaVersion

Added value: +{
+  "const": 2,
+  "type": "number"
+}

changedOutput schema / required

Previous value: -[
-  "contractVersion",
-  "ok",
-  "data"
-]New value: +[
+  "contractVersion",
+  "dataSchemaVersion",
+  "ok",
+  "data"
+]

First observedOct 15, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior: Secret-type vars remain write-only and are unreadable regardless of includeValues, and values are omitted unless explicitly requested. It does not mention rate limits, pagination, or result shape, so it is solid but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, but the body drifts into schema-guardrail prose ("NOT projectName", "NO separate environment param") that repeats the schema's own project description, and the alias sentence is dense shorthand. Every claim is relevant, yet the same information is delivered twice across description and schema.

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

Completeness4/5

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

With 7 params at full schema coverage, an output schema, and read-only annotations, the description only needs to carry the non-obvious gotchas, and it does: alias resolution, decrypt being a deprecated alias for includeValues, and secret write-only limits. Nothing an agent needs to call correctly appears missing.

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 coverage is 100%, so baseline is 3; the description goes beyond it by correcting the param name ("project" NOT "projectName"), warning there is no separate environment param, and supplying the alias expansion table (int→storefront-int, prd/prod, stg/pre) plus a concrete example payload. Those alias mappings are not in the schema and materially affect a correct call.

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?

States a specific verb+resource ("List env vars from the Vercel API") and adds a scope qualifier ("no local infra repo required") that implicitly separates it from the repo-based siblings vercel_env_diff_repo and vercel_env_sources. It never names those siblings explicitly, so an agent still has to infer the boundary, which keeps it below 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?

Gives actionable invocation guidance: set keys + includeValues:true to read decrypted config values, values are omitted by default, and Secret-type vars stay write-only. It does not say when to prefer vercel_env_diff, vercel_env_diff_repo, or vercel_env_sources instead, so the sibling routing is only implied.

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

All Opsphere — DevOps & SRE Intelligence tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?