Skip to main content
Glama

list_service_variables

Retrieve all environment variables for a Railway service to view configuration, audit settings, or check connection strings.

Instructions

[API] List all environment variables for a service

⚡️ Best for: ✓ Viewing service configuration ✓ Auditing environment variables ✓ Checking connection strings

→ Prerequisites: service_list

→ Next steps: variable_set, variable_delete

→ Related: service_info, variable_bulk_set

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesID of the project containing the service
environmentIdYesID of the environment to list variables from (usually obtained from service_list)
serviceIdNoOptional: ID of the service to list variables for, if not provided, shared variables across all services will be listed

Implementation Reference

  • Handler function for the list_service_variables tool, which calls variableService.listVariables with the provided parameters.
    async ({ projectId, environmentId, serviceId }) => {
      return variableService.listVariables(projectId, environmentId, serviceId);
    }
  • Input schema for the tool parameters using Zod.
    {
      projectId: z.string().describe("ID of the project containing the service"),
      environmentId: z.string().describe("ID of the environment to list variables from (usually obtained from service_list)"),
      serviceId: z.string().optional().describe("Optional: ID of the service to list variables for, if not provided, shared variables across all services will be listed")
    },
  • Creates and adds the list_service_variables tool to the variableTools export array.
    createTool(
      "list_service_variables",
      formatToolDescription({
        type: 'API',
        description: "List all environment variables for a service",
        bestFor: [
          "Viewing service configuration",
          "Auditing environment variables",
          "Checking connection strings"
        ],
        relations: {
          prerequisites: ["service_list"],
          nextSteps: ["variable_set", "variable_delete"],
          related: ["service_info", "variable_bulk_set"]
        }
      }),
      {
        projectId: z.string().describe("ID of the project containing the service"),
        environmentId: z.string().describe("ID of the environment to list variables from (usually obtained from service_list)"),
        serviceId: z.string().optional().describe("Optional: ID of the service to list variables for, if not provided, shared variables across all services will be listed")
      },
      async ({ projectId, environmentId, serviceId }) => {
        return variableService.listVariables(projectId, environmentId, serviceId);
      }
    ),
  • The main logic for listing service variables, called by the tool handler. Fetches variables using the client API and formats them for response.
    async listVariables(projectId: string, environmentId: string, serviceId?: string) {
      try {
        const variables = await this.client.variables.getVariables(projectId, environmentId, serviceId);
        
        if (Object.keys(variables).length === 0) {
          return createSuccessResponse({
            text: serviceId
              ? "No variables found for this service in this environment."
              : "No shared variables found in this environment.",
            data: {}
          });
        }
    
        const context = serviceId ? "service variables" : "shared environment variables";
        const formattedVars = Object.entries(variables)
          .map(([key, value]) => `${key}=${value}`)
          .join('\n');
    
        return createSuccessResponse({
          text: `Current ${context}:\n\n${formattedVars}`,
          data: variables
        });
      } catch (error) {
        return createErrorResponse(`Error listing variables: ${formatError(error)}`);
      }
    }
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It implies a read-only operation by using 'List' and 'Viewing', but does not explicitly state whether it's safe, requires authentication, or has rate limits. The description adds some context about listing shared variables if serviceId is omitted, but lacks details on output format or pagination.

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 well-structured with bullet points and icons, making it easy to scan. Every sentence serves a clear purpose—stating the action, providing usage scenarios, and linking to related tools—with no redundant information.

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 tool's moderate complexity (3 parameters, no output schema, no annotations), the description is largely complete. It covers purpose, usage, and parameter nuances, but could improve by addressing behavioral aspects like authentication or output format, which are missing due to the lack of annotations and 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?

The schema description coverage is 100%, so the schema already documents all parameters. The description adds value by clarifying that serviceId is optional and explaining the behavior when omitted (lists shared variables across all services), which enhances understanding beyond the schema's basic descriptions.

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

Purpose5/5

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

The description clearly states the verb ('List') and resource ('all environment variables for a service'), making the purpose specific and unambiguous. It distinguishes itself from sibling tools like service_info or variable_bulk_set by focusing exclusively on listing variables.

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

Usage Guidelines5/5

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

The description provides explicit guidance with 'Best for' scenarios (viewing configuration, auditing, checking connection strings), prerequisites (service_list), next steps (variable_set, variable_delete), and related tools (service_info, variable_bulk_set). This comprehensively informs when and how to use this tool versus alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/epitaphe360/railway-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server