Skip to main content
Glama

delete_modal_secret

Delete a named Modal secret by specifying its name. Optionally target a specific environment to remove the secret from your workspace.

Instructions

Delete a named Modal secret (`modal secret delete`).

Args:
    secret_name: Name of the secret to delete.
    env: Optional Modal environment to target.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
secret_nameYes
envNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations exist; the description carries full burden but only says 'Delete a named Modal secret'. It does not disclose consequences (e.g., irreversibility), required permissions, or side effects. A deletion tool should explicitly state whether the operation is permanent or reversible.

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?

Description is concise with clear sections (action, Args, Returns). No fluff, but the format is straightforward. Could be slightly more structured but achieves brevity effectively.

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

Completeness3/5

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

For a simple deletion tool with 2 params and an output schema, the description is adequate but lacks behavioral details like idempotency, error handling, or permission requirements. It covers the basics but misses context needed for safe invocation.

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

Parameters2/5

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

Schema coverage is 0%, so description must compensate. It provides minimal parameter descriptions: 'Name of the secret to delete' for secret_name and 'Optional Modal environment to target' for env. This adds little beyond schema property names; no info on constraints, format, or examples.

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 clearly states 'Delete a named Modal secret' with a specific verb and resource. It includes the CLI command 'modal secret delete' for reference and distinguishes from sibling tools like create_modal_secret or list_modal_secrets, which handle other operations on secrets.

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 (e.g., when to delete vs. create or list secrets). The description only states the action without context for decision-making.

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