Opsphere — DevOps & SRE Intelligence

Vercel Env vs Repo

vercel_env_diff_repo

Read-only

Compare Vercel runtime env vars with declared repo files. Pass repoDir and repoEnvFiles explicitly for tfvars/HCL; no tenant-specific paths assumed. 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
`teamId`	No	Team ID if applicable
`decrypt`	No	Deprecated alias for includeValues on Vercel side
`project`	Yes	Project name, ID (prj_xxx), or catalog alias (e.g. your-tenant-int, your-tenant-tst)
`repoDir`	No	Repo root to read (required for tfvars unless auto-detected storefront repo)
`context_id`	No	Optional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.
`repoBlocks`	No	HCL block names to parse (default envs only)
`repoEnvFiles`	No	Paths relative to repoDir (e.g. vercel/tfvars/foo.tfvars)
`compareValues`	No	Compare values when Vercel values are readable
`includeValues`	No
`repoEnvFormat`	No		auto
`compareRepoSecrets`	No	Include secrets block values from HCL when true

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_repo",
+  "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 and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond that: it discloses the lack of tenant-specific path assumptions and enumerates the alias normalization rules that silently rewrite input values — the kind of hidden transformation an agent needs to know about.

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?

Three sentences with the core purpose front-loaded, followed by actionable caller guidance and the alias table. The alias enumeration is dense but earns its space since it changes how the `project` argument should be supplied; nothing is redundant.

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 11 parameters, an output schema, and safety annotations in place, the description only needs to cover the tricky parts — and it does: path assumptions and alias normalization. Remaining gaps (whether decryption/secret comparison requires specific Vercel permissions or how mismatches are reported) are minor given the output schema.

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 82%, so the baseline is 3, but the description adds meaningful semantics: the alias-to-canonical-name mapping for `project` (your-tenant-int → your-tenant-storefront-int, prd/prod, stg/pre, test/tst) and the requirement that repoDir/repoEnvFiles be explicit for tfvars/HCL. This goes beyond the schema's terse field descriptions.

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 states a specific verb and both sides of the comparison ("Compare Vercel runtime env vars with declared repo files"), which distinguishes it in resource terms from vercel_env_list and vercel_env_sources. It never names those siblings explicitly, so the differentiation must be inferred from the resource phrasing rather than stated.

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?

It gives procedural guidance ("Pass repoDir and repoEnvFiles explicitly for tfvars/HCL") and notes that no tenant-specific paths are assumed, which implies the tool works without workspace-specific defaults. However, it never says when to prefer this over vercel_env_diff (env-to-env comparison) or vercel_env_sources, and no exclusions or preconditions are stated.

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?