Skip to main content
Glama

service_update

Update a service's configuration in Railway.app to modify settings, resource limits, or deployment parameters for infrastructure management.

Instructions

[API] Update a service's configuration

⚡️ Best for: ✓ Changing service settings ✓ Updating resource limits ✓ Modifying deployment configuration

⚠️ Not for: × Updating environment variables (use variable_set) × Restarting services (use service_restart) × Triggering new deployments (use deployment_trigger)

→ Prerequisites: service_list, service_info

→ Next steps: deployment_trigger

→ Related: service_restart, variable_set

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesID of the project containing the service
serviceIdYesID of the service to update
environmentIdYesID of the environment to update (usually obtained from service_info)
regionNoOptional: Region to deploy the service in
rootDirectoryNoOptional: Root directory containing the service code
buildCommandNoOptional: Command to build the service
startCommandNoOptional: Command to start the service
numReplicasNoOptional: Number of service replicas to run
healthcheckPathNoOptional: Path for health checks
sleepApplicationNoOptional: Whether to enable sleep mode

Implementation Reference

  • Registers the 'service_update' tool with input schema, description, and handler function that calls serviceService.updateService
      "service_update",
      formatToolDescription({
        type: 'API',
        description: "Update a service's configuration",
        bestFor: [
          "Changing service settings",
          "Updating resource limits",
          "Modifying deployment configuration"
        ],
        notFor: [
          "Updating environment variables (use variable_set)",
          "Restarting services (use service_restart)",
          "Triggering new deployments (use deployment_trigger)"
        ],
        relations: {
          prerequisites: ["service_list", "service_info"],
          nextSteps: ["deployment_trigger"],
          related: ["service_restart", "variable_set"]
        }
      }),
      {
        projectId: z.string().describe("ID of the project containing the service"),
        serviceId: z.string().describe("ID of the service to update"),
        environmentId: z.string().describe("ID of the environment to update (usually obtained from service_info)"),
        region: RegionCodeSchema.optional().describe("Optional: Region to deploy the service in"),
        rootDirectory: z.string().optional().describe("Optional: Root directory containing the service code"),
        buildCommand: z.string().optional().describe("Optional: Command to build the service"),
        startCommand: z.string().optional().describe("Optional: Command to start the service"),
        numReplicas: z.number().optional().describe("Optional: Number of service replicas to run"),
        healthcheckPath: z.string().optional().describe("Optional: Path for health checks"),
        sleepApplication: z.boolean().optional().describe("Optional: Whether to enable sleep mode")
      },
      async ({ projectId, serviceId, environmentId, ...config }) => {
        return serviceService.updateService(projectId, serviceId, environmentId, config);
      }
    ),
  • Zod schema defining input parameters for the service_update tool
    {
      projectId: z.string().describe("ID of the project containing the service"),
      serviceId: z.string().describe("ID of the service to update"),
      environmentId: z.string().describe("ID of the environment to update (usually obtained from service_info)"),
      region: RegionCodeSchema.optional().describe("Optional: Region to deploy the service in"),
      rootDirectory: z.string().optional().describe("Optional: Root directory containing the service code"),
      buildCommand: z.string().optional().describe("Optional: Command to build the service"),
      startCommand: z.string().optional().describe("Optional: Command to start the service"),
      numReplicas: z.number().optional().describe("Optional: Number of service replicas to run"),
      healthcheckPath: z.string().optional().describe("Optional: Path for health checks"),
      sleepApplication: z.boolean().optional().describe("Optional: Whether to enable sleep mode")
    },
  • Tool handler function for service_update, delegating to serviceService
    async ({ projectId, serviceId, environmentId, ...config }) => {
      return serviceService.updateService(projectId, serviceId, environmentId, config);
    }
  • Core handler method in ServiceService that performs the service update via the Railway client API, handles errors, and returns formatted response.
    async updateService(projectId: string, serviceId: string, environmentId: string, config: Partial<ServiceInstance>) {
      try {
        const updated = await this.client.services.updateServiceInstance(serviceId, environmentId, config);
        if (!updated) {
          return createErrorResponse(`Error updating service: Failed to update service instance of ${serviceId} in environment ${environmentId}`);
        }
    
        return createSuccessResponse({
          text: `Service configuration updated successfully`
        });
      } catch (error) {
        return createErrorResponse(`Error updating service: ${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 of behavioral disclosure. It implies mutation ('Update'), but doesn't specify permissions required, whether changes are reversible, or potential side effects (e.g., downtime). However, it adds some context by listing prerequisites and related tools, which helps infer workflow dependencies. Without annotations, more behavioral details (e.g., rate limits, auth needs) would improve transparency.

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 and front-loaded with the core purpose, followed by clear sections (Best for, Not for, Prerequisites, Next steps, Related). Every sentence earns its place by providing actionable guidance without redundancy. It uses bullet points and symbols (✓, ×, →) for readability, making it efficient and easy to scan.

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 complexity (10 parameters, mutation operation) and lack of annotations/output schema, the description does a good job of contextual completeness by covering usage guidelines, exclusions, prerequisites, and related tools. However, it could be more complete by including details on behavioral traits (e.g., what 'Update' entails operationally) or output expectations, which are missing despite no output schema.

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 description coverage is 100%, so the schema already documents all 10 parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema (e.g., no extra syntax or format details). According to the rules, with high schema coverage (>80%), the baseline is 3 even with no param info in the description, which applies here.

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 tool's purpose with specific verbs ('Update a service's configuration') and distinguishes it from sibling tools by listing what it's 'Not for' (e.g., not for updating environment variables, restarting services, or triggering deployments). It explicitly names alternative tools like variable_set, service_restart, and deployment_trigger, making its scope unambiguous.

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 on when to use this tool ('Best for: Changing service settings, Updating resource limits, Modifying deployment configuration') and when not to use it ('Not for: Updating environment variables, Restarting services, Triggering new deployments'), with named alternatives for each exclusion. It also lists prerequisites (service_list, service_info) and next steps (deployment_trigger), offering comprehensive usage context.

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