Skip to main content
Glama
michaelneale

Goose App Maker MCP

by michaelneale

app_error

Report app errors or retrieve error lists for development and debugging in Goose App Maker MCP applications.

Instructions

Report an error from the app or retrieve the list of errors.
This is useful while developing or debugging the app as it allows errors (or any messages) to be reported and monitored

Args:
    error_message: Optional error message to report. If None, returns the list of errors.
    clear: Optional, If True, clears the list of errors

Returns:
    A string containing the list of errors if error_message is None,
    otherwise a confirmation message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
error_messageNo
clearNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:667-715 (handler)
    The main handler function for the app_error tool. It reports new errors to a global list or retrieves and formats the list of existing errors. Supports clearing the list.
    def app_error(error_message: str = None, clear = False) -> str:
        """
        Report an error from the app or retrieve the list of errors.
        This is useful while developing or debugging the app as it allows errors (or any messages) to be reported and monitored
        
        Args:
            error_message: Optional error message to report. If None, returns the list of errors.
            clear: Optional, If True, clears the list of errors
        
        Returns:
            A string containing the list of errors if error_message is None,
            otherwise a confirmation message.
        """
        global app_errors
    
        
        try:
            # If no error message is provided, return the list of errors
            if error_message is None:
                # if app errors is empty
                if not app_errors:
                   return "No errors reported. If needed, consider adding in some calls to reportError() in your app code to help with debugging."
                
                # Format the errors as a numbered list
                error_list = "\n".join([f"{i+1}. {err}" for i, err in enumerate(app_errors)])
    
                if clear:
                    app_errors.clear()
    
                return f"Reported errors:\n{error_list}"
            
            if clear:
                app_errors.clear()
    
            # Add the error to the list with a timestamp
            timestamp = time.strftime("%Y-%m-%d %H:%M:%S")
            app_errors.append(f"[{timestamp}] {error_message}")
            
            # Keep only the last 100 errors to prevent unbounded growth
            if len(app_errors) > 100:
                app_errors = app_errors[-100:]
            
            logger.warning(f"App error reported: {error_message}")
            return f"Error reported: {error_message}"
        
        except Exception as e:
            logger.error(f"Error handling app_error: {e}")
            return f"Failed to process error: {str(e)}"
  • main.py:666-666 (registration)
    Registers the app_error function as a tool in the FastMCP server using the @mcp.tool() decorator.
    @mcp.tool()
  • main.py:42-43 (helper)
    Global list used by the app_error tool to store and manage reported errors from the web app.
    # Global variable to store app errors
    app_errors = []
  • Type signature and docstring defining the input parameters (error_message: str optional, clear: bool) and output (str) for the tool.
    def app_error(error_message: str = None, clear = False) -> str:
        """
        Report an error from the app or retrieve the list of errors.
        This is useful while developing or debugging the app as it allows errors (or any messages) to be reported and monitored
        
        Args:
            error_message: Optional error message to report. If None, returns the list of errors.
            clear: Optional, If True, clears the list of errors
        
        Returns:
            A string containing the list of errors if error_message is None,
            otherwise a confirmation message.
        """
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the tool's dual behavior (reporting vs. retrieving) and mentions clearing errors, which adds context. However, it doesn't cover aspects like permissions needed, rate limits, or whether operations are persistent, leaving gaps in behavioral understanding.

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, with the core purpose stated first. The Args and Returns sections are structured but could be more integrated; however, every sentence adds value without redundancy, making it efficient overall.

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?

Given the tool's moderate complexity (dual functionality, 2 parameters), no annotations, and an output schema present, the description is fairly complete. It explains parameters, return values, and usage context, though it could benefit from more behavioral details like error handling or persistence.

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?

The description adds significant meaning beyond the input schema, which has 0% coverage. It explains that 'error_message' is optional and determines the tool's mode (report if provided, retrieve if None), and that 'clear' is optional and clears the list if True. This fully compensates for the lack of schema descriptions.

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 dual purpose: 'Report an error from the app or retrieve the list of errors.' It specifies the verb (report/retrieve) and resource (errors), though it doesn't explicitly differentiate from sibling tools like app_response or app_list, which might handle other app-related operations.

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

Usage Guidelines3/5

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

The description provides implied usage context: 'useful while developing or debugging the app.' However, it lacks explicit guidance on when to use this tool versus alternatives (e.g., app_response for general responses or app_list for listing other items) and does not specify prerequisites or exclusions.

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