Skip to main content
Glama

list_modal_resources

Read-onlyIdempotent

Look up Modal apps, containers, volumes, secrets, environments, and profiles in read-only mode to find the names and IDs other tools require.

Instructions

Read-only lookup of everything in the Modal account. Start here to find the app name,
container ID or volume name that the other tools take.

Args:
    resource: One of:
        "apps" — deployed/running/recently-stopped apps.
        "app_history" — one app's deployment versions (`name` = app name/ID); use it
            to pick a version for manage_modal_app(action="rollback").
        "containers" — running containers ("ta-..."); `name` = app ID to filter.
        "volumes" — named volumes.
        "volume_files" — files in a volume (`name` = volume, plus `path`).
        "secrets" — secret names only; values are never returned.
        "environments" — valid values for every `env` argument.
        "profile" — active profile + all profiles (which account am I?).
    name: App name/ID, app ID filter, or volume name — see `resource`.
    path: Path inside the volume for "volume_files". Default "/".
    env: Modal environment. Ignored for "environments"/"profile".
    profile: Modal profile for this call only. Defaults to the active profile.

Returns: {<resource key>: [...]} — e.g. "apps", "containers", "contents". Listings
over 200 entries are capped, with `omitted_items` giving the count dropped.

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": {
      "resource": "<resource>"
    },
    "name": "list_modal_resources"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNo
nameNo
pathNo/
profileNo
resourceYes

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.9/5.0
Behavior5/5

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

Goes well beyond the readOnly/destructive/idempotent annotations by disclosing that secret values are never returned, that env is ignored for "environments"/"profile", and that listings over 200 entries are capped with `omitted_items` giving the dropped count. These are non-obvious behaviors an agent must know before trusting the output.

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 purpose and routing sentence before the argument breakdown; every line of the resource list earns its place by resolving an ambiguity the schema leaves open. Slightly long at the argument block, and the trailing Returns line duplicates output-schema territory, but there is no filler.

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?

For a 5-parameter, implicitly-enumerated read tool, everything an agent needs to select the right resource and interpret defaults is present, in addition to the return key shape and truncation behavior. An output schema exists, so the brief Returns note is a convenience rather than a gap.

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 coverage is 0% and `resource` has no enum in the schema, so the description carries the full burden — and does: it enumerates all eight resource values with per-value meaning and notes `name` is interpreted differently per resource (app name/ID, app ID filter, or volume). It also covers path default, env being ignored for two resources, and profile defaulting to active.

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?

Opens with a specific verb and scope — 'Read-only lookup of everything in the Modal account' — then names the exact tokens (app name, container ID, volume name) other tools consume. This clearly separates it from siblings like manage_modal_app or inspect_modal_secret without opening any schema.

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: 'Start here to find the app name, container ID or volume name that the other tools take,' and pins a concrete handoff case to manage_modal_app(action="rollback") via app_history. Both when-to-use and which-alternative scenarios are stated.

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