Skip to main content
Glama

Delete a Hosted App

delete_app
DestructiveIdempotent

Delete a Hosted App and every stored version and file.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "delete_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoApp slug; provide exactly one of slug or app_id
app_idNoApp UUID; provide exactly one of slug or app_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so safety is covered. The description adds the important detail that deletion cascades to all versions and files, which is exactly the extra context an agent needs before calling. It stops short of saying whether the deletion is irreversible or what happens when the app is not found.

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?

One front-loaded sentence with no waste. The destructive scope is stated immediately, which is the right priority for a delete tool.

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?

For a two-parameter destructive tool whose annotations carry the safety profile and whose schema fully documents inputs, the description covers the essential unknown: cascade scope. Missing only irreversibility and not-found behavior, which are minor here.

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

Parameters3/5

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

Schema coverage is 100% and the schema already documents the slug/app_id mutual-exclusivity ('provide exactly one of slug or app_id'), so the description need not repeat it. The description adds no parameter meaning beyond the schema, which is the baseline case.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Delete a Hosted App') and adds scope ('every stored version and file'), which implicitly distinguishes it from delete_app_version. It does not name that sibling explicitly, so the differentiation is inferable rather than stated.

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?

There is no when-to-use guidance, no prerequisites, and no explicit pointer to the narrower alternative (delete_app_version / delete_app_version-style tools) for removing a single version. The agent must infer usage purely from the cascade scope clause.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources