Skip to main content
Glama
michaelneale

Goose App Maker MCP

by michaelneale

app_refresh

Refresh the currently open Chrome app on macOS to apply changes or restart the application.

Instructions

Refresh the currently open app in Chrome.
Only works on macOS with Google Chrome.

Returns:
    A dictionary containing the result of the operation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:583-613 (handler)
    The handler function for the 'app_refresh' tool. It is registered via the @mcp.tool() decorator. The function refreshes the active tab in Google Chrome using AppleScript, but only on macOS systems.
    @mcp.tool()
    def app_refresh() -> Dict[str, Any]:
        """
        Refresh the currently open app in Chrome.
        Only works on macOS with Google Chrome.
        
        Returns:
            A dictionary containing the result of the operation
        """
        try:
            # Check if we're on macOS
            if os.uname().sysname != "Darwin":
                return {
                    "success": False,
                    "error": "This function is only available on macOS"
                }
            
            # Use AppleScript to refresh the active tab in Chrome
            refresh_script = 'tell application "Google Chrome" to tell active tab of front window to reload'
            # Use Popen instead of run to avoid blocking
            subprocess.Popen(["osascript", "-e", refresh_script], 
                             stdout=subprocess.DEVNULL, 
                             stderr=subprocess.DEVNULL)
            
            return {
                "success": True,
                "message": "App refreshed successfully in Chrome"
            }
        except Exception as e:
            logger.error(f"Error refreshing app: {e}")
            return {"success": False, "error": f"Failed to refresh app: {str(e)}"}
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses platform/software constraints (macOS/Chrome) and mentions the return format, but doesn't cover other behavioral aspects like error handling, permissions needed, or what 'refresh' entails operationally (e.g., reloads page, clears cache).

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?

The description is appropriately sized with three concise sentences that each add value: stating the action, specifying constraints, and describing the return. It's front-loaded with the core purpose and wastes no words.

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 0 parameters, 100% schema coverage, and an output schema (which handles return values), the description is reasonably complete. It covers the tool's purpose, operational constraints, and mentions the return format. However, for a tool with no annotations, it could benefit from more behavioral context about what 'refresh' actually does.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, maintaining focus on the tool's purpose and constraints.

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 action ('Refresh') and target ('the currently open app in Chrome'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'app_open' or 'app_stop_server' in terms of when to use one versus the other.

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?

The description provides clear context about when this tool works ('Only works on macOS with Google Chrome'), which is helpful for usage decisions. However, it doesn't explicitly state when to use this versus alternatives like 'app_open' or 'app_stop_server' from the sibling list.

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