Skip to main content
Glama
george-bobby

Modal MCP

by george-bobby
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_modal_resources

Read-onlyIdempotent

Inspect Modal account resources: apps, containers, volumes, secrets, environments, profiles. Get names and IDs needed by other Modal tools from a read-only lookup.

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".

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
envNo
nameNo
pathNo/
resourceYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.2

TDQS

A5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, and the description adds substantial behavioral context beyond that: 200-entry cap with omitted_items, the return shape, that secret values are never returned, and that env is ignored for 'environments'/'profile'. This fully discloses what happens when the tool is invoked.

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 detailed yet tightly structured with a front-loaded purpose line and a bulleted resource list. Every sentence adds operational value; no filler or redundant restatement of the name/schema exists.

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 broad read-only lookup tool, the description covers purpose, all parameter behaviors, return format, pagination truncation, and caveats like secret value redaction. An agent has enough context to select the right resource and correctly interpret results without opening the output schema.

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%, but the description compensates completely by documenting every parameter: the full set of resource enum values, the polymorphic meaning of name, the path default, and when env applies. It adds meaning far beyond the raw schema properties.

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 opens with a specific verb and resource ('Read-only lookup of everything in the Modal account') and enumerates eight clearly differentiated resource types. It distinguishes this discovery tool from the sibling action tools by positioning it as the starting point to find identifiers those tools consume.

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 explicitly says 'Start here to find the app name, container ID or volume name that the other tools take,' and each resource option includes its intended use, such as using 'app_history' to pick a version for manage_modal_app(action='rollback'). It also gives exclusions, e.g. secrets return names only and env is ignored for certain resources.

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

Deploy Server

Other Tools