Opsphere — DevOps & SRE Intelligence

Vercel Project Status

vercel_project_status

Read-only

Quick status: env summary + latest deploys (date/author/commit/branch). 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
`search`	No	If no project given, filter project list by this text
`teamId`	No	Team ID if applicable
`project`	No	Project name, ID, or catalog alias (e.g. your-tenant-int, your-tenant-pre)
`context_id`	No	Optional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.
`deployLimit`	No

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_project_status",
+  "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

Behavior4/5

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

Annotations already declare this as a safe read-only, non-destructive operation with a closed-world scope, so the safety profile is covered. The description adds useful behavioral context by explaining that the result combines environment summary and latest deploy details including date, author, commit, and branch, and by documenting alias normalization.

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

Conciseness5/5

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

The description is front-loaded with the main purpose and then compactly lists output contents and alias behavior. It is appropriately sized with no redundant sentences.

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?

Given the read-only annotations, 80% schema description coverage, and the presence of an output schema, the description is largely complete for invoking the tool correctly. Its main remaining gap is routing guidance against closely related Vercel siblings.

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 high at 80%, so the baseline is 3, but the description adds meaningful alias semantics beyond the schema: specific tenant aliases and environment shorthand such as prd/prod, stg/pre, and test/tst. It does not explain deployLimit or the search/team/context parameters, but those are largely covered by the schema.

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 clear composite purpose: a quick Vercel project status covering environment summary plus latest deploy metadata (date/author/commit/branch). It is more specific than a bare title, but it does not explicitly distinguish this tool from sibling tools such as vercel_deploys_latest or vercel_env_list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'Quick status' implies an overview use case, but there is no explicit guidance on when to use this tool versus vercel_deploys_latest, vercel_env_list, or other Vercel siblings. No exclusions or alternatives are named, so the agent must infer routing from the composite output description.

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?