Railway MCP Server

volume_delete

Delete a volume from a Railway service to remove unused storage and manage resources. Use for storage cleanup after backing up data.

Instructions

[API] Delete a volume from a service

⚡️ Best for: ✓ Removing unused storage ✓ Storage cleanup ✓ Resource management

⚠️ Not for: × Temporary data removal × Data backup (use volume_backup first)

→ Prerequisites: volume_list

→ Related: service_update

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "volumeId": "<volumeId>"
    },
    "name": "volume_delete"
  }
}

Input Schema

Name	Required	Description	Default
`volumeId`	Yes	ID of the volume to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 6, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It confirms deletion but lacks details on permissions, irreversibility, or side effects. Adequate but not rich.

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?

Concise, well-organized with bullet points and emojis. Every sentence adds value with no redundancy.

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?

Covers prerequisites and related tools. For a simple delete action with one parameter, it is fairly complete, though lacks info on synchronous behavior or return value.

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?

Only one parameter with schema covering its description fully. The description adds no extra semantic value beyond 'ID of the volume to delete'.

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 explicitly states 'Delete a volume from a service' with clear verb and resource. It distinguishes from related tools like volume_backup for data backup, making the purpose 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?

Provides explicit best-for and not-for sections, lists prerequisites (volume_list) and related tool (service_update), giving clear guidance on when and when not to use.

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