Opsphere — DevOps & SRE Intelligence

Railway dashboard

railway_dashboard

Read-only

Aggregated view across accessible projects (max 20). Limited concurrency; continues on per-project failures.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "railway_dashboard"
  }
}

Input Schema

Name	Required	Description	Default
`since`	No
`context_id`	No	Optional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.
`detail_level`	No		summary
`workspace_id`	No
`project_limit`	No
`include_healthy`	No

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026
RemovedOct 19, 2026
First observedOct 15, 2026

TDQS

C2.9/5.0

Behavior4/5

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

Annotations already establish that the tool is read-only, non-destructive, and closed-world. The description adds useful behavior beyond that: it discloses limited concurrency and that execution continues on per-project failures, which is valuable for an aggregating tool.

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 two short sentences with no filler, and the core capability is front-loaded before operational caveats. Every sentence provides either scope or behavior information.

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

Completeness2/5

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

An output schema exists, so return values need not be described. Still, for a dashboard-style aggregation tool with six parameters and low schema coverage, the description omits what data the dashboard contains and how to choose among the many sibling railway tools.

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?

With only 17% schema description coverage across six parameters, the description should compensate but does not. It hints at a project limit through '(max 20)', which is already encoded in the schema, and leaves since, detail_level, workspace_id, and include_healthy unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it provides an aggregated view across accessible projects with a maximum of 20, which gives a general sense of purpose. However, it does not specify what is being aggregated (health, deployments, metrics, etc.) or distinguish the tool from siblings such as railway_health_summary or railway_projects_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?

There is no explicit guidance on when to use this tool versus alternatives, nor any stated prerequisites or exclusions. The notes about concurrency and failure handling are operational behavior, not usage selection guidance.

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?