Skip to main content
Glama

manage_modal_volume

Destructive

Create, delete, or rename Modal volumes in a specified environment for lifecycle management. Use separate file tools to read or write contents inside a volume.

Instructions

Volume lifecycle. For the files inside a volume use modal_volume_files (writes) or
list_modal_resources(resource="volume_files") (reads).

Args:
    action: "create", "delete" (removes the volume and ALL its data — irreversible),
        or "rename".
    volume_name: Volume name (the current name, for "rename").
    new_name: Required for "rename".
    env: Modal environment. Volumes are environment-scoped, so this must match the
        environment the volume lives in.
    profile: Modal profile for this call only. Defaults to the active profile.

Returns: {message, stdout, stderr} or {error}.

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": {
      "action": "<action>",
      "volume_name": "<volume_name>"
    },
    "name": "manage_modal_volume"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNo
actionYes
profileNo
new_nameNo
volume_nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.1
    • addedInput schema / properties / profile
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Profile"
      +}
  2. Addedv0.2.2

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description still adds specificity by warning that delete removes the volume and ALL its data and is irreversible, plus the env-matching precondition. It does not cover idempotency (annotation handles that) or intermediate stdout behavior on long operations, keeping it just short of a 5.

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

Conciseness4/5

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

Front-loaded with the routing rule, then Args, then Returns — a clean structure with no wasted sentences. Minor deduction for the elliptical 'Volume lifecycle.' opener and the Returns line, which duplicates the output schema without adding provisional detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

All five parameters, the destructive semantics of delete, the env precondition, sibling routing, and the return shape are covered; the existence of an output schema means no further return-value explanation is required. Nothing an agent needs to call this correctly is missing.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must carry the parameter burden, and it does: action enumerates the three valid values, volume_name is identified as the current name for rename, new_name is marked required for rename, env is environment-scoped, and profile is scoped to this call only with a stated default.

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?

States a specific verb set and resource ('Volume lifecycle' with create/delete/rename actions) and draws a hard boundary against the file-level siblings (modal_volume_files, list_modal_resources). An agent can tell immediately that this tool manages the volume object itself, not its contents.

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?

Explicitly routes the agent: for files inside a volume use modal_volume_files (writes) or list_modal_resources(resource="volume_files") (reads). It also flags the env-scoping requirement ('must match the environment the volume lives in'), which is exactly the precondition that causes failures when ignored.

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