Opsphere — DevOps & SRE Intelligence

Vercel Env Diff

vercel_env_diff

Read-only

Compare env vars between two Vercel projects (targets/types, optional value diff). 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
`teamId`	No	Team ID if applicable
`projectA`	Yes	Project A (name, ID, or catalog alias e.g. your-tenant-int)
`projectB`	Yes	Project B (name, ID, or brand alias e.g. your-tenant-int)
`context_id`	No	Optional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.
`compareValues`	No	Requires decrypt permissions

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_diff",
+  "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.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and closed-world, so safety is covered. The description adds genuinely new behavior: alias resolution rules (your-tenant-int → your-tenant-storefront-int, prd/prod, stg/pre, test/tst) that tell the agent how project identifiers are normalized before comparison.

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?

Two front-loaded sentences with the comparison scope stated first and the alias mechanics second; no filler. The alias clause is a bit list-heavy and could be tabled, but nothing is wasted.

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?

Output schema exists, so return-value explanation is not required, and safety is fully covered by annotations. What remains missing is any hint about how to read the comparison or when this tool is preferable to vercel_env_diff_repo — a minor gap for an otherwise well-specified read-only tool.

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 3 applies, but the description contributes above that: it enumerates concrete brand-alias expansions and environment shorthand mappings that the schema only gestures at with "catalog alias e.g. your-tenant-int". It also flags that value diffing is optional, matching compareValues' default false.

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 ("Compare env vars between two Vercel projects") and scopes what is compared (targets/types, optional value diff). It does not, however, distinguish itself from the close sibling vercel_env_diff_repo or position itself against vercel_env_list/vercel_env_sources, so the agent must infer the boundary.

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?

Usage is only implied: the two-project comparison is self-explanatory, but there is no explicit statement of when to choose this over vercel_env_diff_repo, vercel_env_list, or vercel_env_sources, and no prerequisites beyond what the schema says about decrypt permission.

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?