Skip to main content
Glama
michaelneale

Goose App Maker MCP

by michaelneale

app_delete

Remove a web application from the Goose App Maker MCP server by specifying its name to manage your application portfolio.

Instructions

Delete an existing web application.

Args:
    app_name: Name of the application to delete

Returns:
    A dictionary containing the result of the operation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:164-194 (handler)
    The main handler function for the 'app_delete' tool. It is registered via the @mcp.tool() decorator. The function deletes the directory of the specified app using shutil.rmtree if it exists, returning success or error status.
    @mcp.tool()
    def app_delete(app_name: str) -> Dict[str, Any]:
        """
        Delete an existing web application.
        
        Args:
            app_name: Name of the application to delete
        
        Returns:
            A dictionary containing the result of the operation
        """
        try:
            # Find the app directory
            app_path = os.path.join(APP_DIR, app_name)
            if not os.path.exists(app_path):
                return {
                    "success": False, 
                    "error": f"App '{app_name}' not found at {app_path}"
                }
            
            # Delete the app directory
            shutil.rmtree(app_path)
            
            return {
                "success": True,
                "app_name": app_name,
                "message": f"App '{app_name}' deleted successfully"
            }
        except Exception as e:
            logger.error(f"Error deleting app: {e}")
            return {"success": False, "error": f"Failed to delete app: {str(e)}"}
  • main.py:164-164 (registration)
    The @mcp.tool() decorator registers the app_delete function as an MCP tool.
    @mcp.tool()
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool deletes an app, implying a destructive mutation, but doesn't describe what 'delete' entails (e.g., irreversible removal, cleanup of resources, permissions required, or error handling). This leaves gaps in understanding the tool's behavior beyond the basic action.

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?

The description is appropriately sized and front-loaded: the first sentence states the purpose clearly, followed by structured sections for Args and Returns. There's no wasted text, and the structure aids readability, though the Returns section is vague ('A dictionary containing the result of the operation').

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?

Given the tool's complexity (destructive operation with 1 parameter) and context (no annotations, schema coverage 0%, but has output schema), the description is minimally adequate. It covers the basic action and parameter, but lacks details on behavior, usage, and output specifics, even though the output schema might document return values. For a deletion tool, more guidance is needed.

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?

The description adds minimal semantics: it names the parameter ('app_name') and indicates it's 'Name of the application to delete.' With 0% schema description coverage, the schema provides no details, so the description compensates slightly by clarifying the parameter's role. However, it doesn't explain format, constraints, or examples, leaving the parameter only partially documented.

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?

The description clearly states the tool's purpose: 'Delete an existing web application.' It specifies the verb ('Delete') and resource ('web application'), making the action unambiguous. However, it doesn't differentiate from sibling tools like 'app_stop_server' or 'app_error', which might also involve application management, so it doesn't fully distinguish from alternatives.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., the app must exist or be stopped), exclusions (e.g., don't use if the app is running), or refer to sibling tools like 'app_list' to check before deletion. Usage is implied by the purpose but lacks explicit context.

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/michaelneale/goose-app-maker-mcp'

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