Skip to main content
Glama

volume_update

Modify volume properties in Railway infrastructure by changing the name or updating configurations to manage storage resources.

Instructions

Update a volume's properties

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
volumeIdYesID of the volume to update
nameYesNew name for the volume

Implementation Reference

  • MCP tool 'volume_update' handler implementation: validates input with Zod schema and delegates to volumeService.updateVolume(volumeId, name). This is the core execution logic for the tool.
    createTool(
      "volume_update",
      "Update a volume's properties",
      {
        volumeId: z.string().describe("ID of the volume to update"),
        name: z.string().describe("New name for the volume")
      },
      async ({ volumeId, name }) => {
        return volumeService.updateVolume(volumeId, name);
      }
    ),
  • Registers all tools, including volumeTools containing 'volume_update', to the MCP server by spreading volumeTools into allTools and calling server.tool() for each.
    export function registerAllTools(server: McpServer) {
      // Collect all tools
      const allTools = [
        ...databaseTools,
        ...deploymentTools,
        ...domainTools,
        ...projectTools,
        ...serviceTools,
        ...tcpProxyTools,
        ...variableTools,
        ...configTools,
        ...volumeTools,
        ...templateTools,
      ] as Tool[];
    
      // Register each tool with the server
      allTools.forEach((tool) => {
        server.tool(
          ...tool
        );
      });
    } 
  • TypeScript interface defining the input structure for volume updates, used in repository and service layers.
    export interface VolumeUpdateInput {
      name: string;
    }
  • volumeService.updateVolume: wraps the repository call, handles errors, and formats the MCP CallToolResult response.
    async updateVolume(volumeId: string, name: string): Promise<CallToolResult> {
      try {
        const input = { name };
        const volume = await this.client.volumes.updateVolume(volumeId, input);
        
        return createSuccessResponse({
          text: `✅ Volume updated successfully to "${volume.name}" (ID: ${volume.id})`,
          data: volume
        });
      } catch (error) {
        return createErrorResponse(`Error updating volume: ${formatError(error)}`);
      }
    }
  • Repository layer GraphQL mutation execution for updating volume details.
    async updateVolume(volumeId: string, input: VolumeUpdateInput): Promise<Volume> {
      const data = await this.client.request<{ volumeUpdate: Volume }>(`
        mutation volumeUpdate($input: VolumeUpdateInput!, $volumeId: String!) {
          volumeUpdate(input: $input, volumeId: $volumeId) {
            createdAt
            id
            name
            projectId
          }
        }
      `, { input, volumeId });
    
      return data.volumeUpdate;
    }
Behavior2/5

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

With no annotations, the description carries full burden but only states it's an update operation. It lacks critical behavioral details: whether this requires specific permissions, if changes are reversible, potential side effects, or error conditions. 'Update' implies mutation, but no further context is given.

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 a single, efficient sentence with no wasted words. It's front-loaded with the core action and resource, making it easy to scan and understand quickly.

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?

Given the tool's complexity (a mutation operation with no annotations and no output schema), the description is insufficient. It doesn't explain what happens on success/failure, return values, or behavioral nuances, leaving significant gaps for an agent to use 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 description coverage is 100%, so the schema fully documents both parameters (volumeId and name). The description adds no additional meaning beyond the schema's parameter descriptions, such as format examples or constraints, but doesn't contradict them either.

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?

The description clearly states the action ('Update') and resource ('a volume's properties'), making the purpose evident. However, it doesn't differentiate from sibling tools like 'volume_create' or 'volume_delete' beyond the verb, nor does it specify what 'properties' means beyond the schema's 'name' parameter.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing volume), exclusions, or comparisons to siblings like 'volume_create' for new volumes or 'volume_list' for viewing properties.

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