Opsphere — DevOps & SRE Intelligence

Railway project status

railway_project_status

Read-only

Operational summary for a Railway project: environments, services, latest deployments, optional domains/volumes. SUCCESS does not prove HTTP health.

Input Schema

Name	Required	Description
`project`	Yes
`context_id`	No	Optional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.
`environment`	No
`include_domains`	No
`include_volumes`	No
`deployment_limit`	No

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed23 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 / deployment

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

removedOutput schema / properties / data / properties / deployments

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

removedOutput schema / properties / data / properties / environments

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

addedOutput schema / properties / data / properties / family

Added value: +{
+  "const": "railway",
+  "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/projects"
-}

removedOutput schema / properties / data / properties / logs

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

addedOutput schema / properties / data / properties / operation

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

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

removedOutput schema / properties / data / properties / projects

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

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"
+}

removedOutput schema / properties / data / properties / services

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

removedOutput schema / properties / data / properties / status
```
Removed value: -{
-  "type": "string"
-}
```
addedOutput schema / properties / data / properties / summary
```
Added value: +{
+  "type": "string"
+}
```
removedOutput schema / properties / data / properties / text
```
Removed 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.5/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 a genuinely useful outcome caveat—'SUCCESS does not prove HTTP health'—which tells the agent not to treat deployment success as service health, and it discloses that domains/volumes are optional inclusions.

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?

Two tight sentences with zero waste: the contents are front-loaded and the health caveat follows. Nothing is repeated from the title or schema.

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

Completeness3/5

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

An output schema exists and the description appropriately describes what the summary contains rather than return values. However, for a 6-parameter tool it omits the environment filter semantics, deployment_limit behavior, and project identifier format, and gives no sibling-routing guidance, leaving meaningful gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 17%, so the description must compensate and largely does not. It names domains/volumes and deployments conceptually but never maps them to include_domains/include_volumes/deployment_limit, and it leaves the environment filter and required project identifier unexplained, leaving 5 of 6 parameters undocumented.

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 (operational summary) and resource (Railway project), and enumerates the contents (environments, services, deployments, optional domains/volumes), which differentiates it from sibling list tools like railway_projects_list and railway_environments_list. It stops short of explicitly saying it aggregates one project where those siblings enumerate many.

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 implied by 'for a Railway project', but the description never says when to choose this over railway_environments_list, railway_services_list, or railway_projects_list. No exclusions or selection conditions are given.

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?