Skip to main content
Glama

Opsphere — DevOps & SRE Intelligence

Railway services list

railway_services_list
Read-only

List services (and service instances) in a project. Optional environment filter and latest deployment summary.

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
projectYesProject ID or name
context_idNoOptional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.
environmentNoEnvironment ID or name
include_latest_deploymentNo

Output Schema

NameRequiredDescriptionDefault
okYes
dataYes
contractVersionYes
dataSchemaVersionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed23 schema fields changed
    • 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_services_list",
      +  "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"
      +]
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds that service instances are included and that a deployment summary can be attached, but says nothing about pagination, result ordering, or failure behavior for an unknown project.

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

Conciseness3/5

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

Two short sentences, front-loaded with the core action, with no filler. However, 'Optional environment filter' largely restates the schema description 'Environment ID or name' and the second sentence is telegraphic rather than informative, so not every clause earns its place.

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, so return values need not be described, and the annotations cover safety. Still, for a 6-parameter tool with half the parameters undocumented, the description leaves the agent guessing about paging ('limit') and name filtering ('query'), which are relevant to calling it correctly.

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

Parameters3/5

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

Schema coverage is 50%: project, environment and context_id are documented in the schema, while limit, query and include_latest_deployment are not. The description partly compensates by explaining the environment filter and the optional latest-deployment summary, but 'limit' and 'query' remain undocumented anywhere, so it does not fully close the gap.

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 and resource ('List services (and service instances)') with the scoping context 'in a project', which is enough to distinguish it from railway_projects_list and railway_environments_list. It does not explicitly name those siblings, so the differentiation is inferential 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?

The phrase 'in a project' implies the required precondition, and mentioning the environment filter hints at when the extra param is useful. But there is no explicit when-to-use/when-not, no guidance on preferring this over railway_project_status, and no mention of what to do if the project is ambiguous (ID vs name).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources