Skip to main content
Glama
george-bobby

Modal MCP

by george-bobby
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

rollback_modal_app

Revert a Modal app to an earlier deployment version by specifying the app identifier and optionally a version number. Use to undo problematic deployments.

Instructions

Roll a Modal app back to a previous deployment version (`modal app rollback`).

Args:
    app_identifier: App name or app ID.
    version: Optional specific version to roll back to. If omitted, Modal rolls back
        to the immediately preceding version. Use get_modal_app_history to list versions.
    env: Optional Modal environment to target.

Returns:
    A dictionary containing the result of the rollback operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_identifierYes
versionNo
envNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4/5.0
Behavior2/5

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

No annotations provided. Describes parameters but lacks details on side effects, permissions, or limitations beyond basic rollback operation. For a mutation tool, more transparency is needed.

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, front-loaded with main action, parameter descriptions, and return type. No unnecessary information.

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 all parameters and return type. Lacks behavioral context (e.g., prerequisites, idempotency), but overall sufficient for a simple 3-parameter tool with output schema.

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

Parameters4/5

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

Adds significant value beyond schema by explaining default behavior for version and referencing an auxiliary tool. With 0% schema coverage, description compensates well.

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?

Description clearly states 'Roll a Modal app back to a previous deployment version' with the command name and distinguishes it from siblings like deploy, run, stop.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Suggests using get_modal_app_history to list versions, providing helpful context. However, does not explicitly contrast with alternative tools for different actions.

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/george-bobby/mcp-modal'

If you have feedback or need assistance with the MCP directory API, please join our Discord server