Skip to main content
Glama
es6kr

claude-session-manager

by es6kr

stop_gui

Stop the Claude Code Session Manager web interface to end GUI server sessions and free system resources.

Instructions

Stop the web GUI server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The function that executes the stop_gui tool logic: terminates the global web server subprocess gracefully or forcefully.
    def stop_web_gui() -> dict:
        """Stop the web GUI server."""
        global _web_server_process
    
        if _web_server_process is None or _web_server_process.poll() is not None:
            _web_server_process = None
            return {
                "success": True,
                "message": "Web GUI is not running"
            }
    
        try:
            _web_server_process.terminate()
            _web_server_process.wait(timeout=5)
            _web_server_process = None
            return {
                "success": True,
                "message": "Web GUI stopped successfully"
            }
        except subprocess.TimeoutExpired:
            _web_server_process.kill()
            _web_server_process = None
            return {
                "success": True,
                "message": "Web GUI forcefully stopped"
            }
        except Exception as e:
            return {
                "success": False,
                "message": f"Failed to stop web GUI: {str(e)}"
            }
  • Registration of the stop_gui tool with the MCP server in the list_tools function, including its input schema (no parameters).
    Tool(
        name="stop_gui",
        description="Stop the web GUI server",
        inputSchema={
            "type": "object",
            "properties": {},
            "required": []
        }
    )
  • Dispatch handler in the main call_tool function that invokes stop_web_gui when the tool name matches.
    elif name == "stop_gui":
        result = stop_web_gui()
  • Global variable used by stop_gui (and start_gui) to track and manage the web server process.
    _web_server_process: subprocess.Popen | None = None
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action ('Stop') which implies a mutation, but doesn't describe effects like whether the GUI shuts down gracefully, requires specific permissions, impacts other sessions, or provides any confirmation. This leaves significant gaps for a mutation tool.

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 a single, efficient sentence with zero wasted words. It's front-loaded with the core action and resource, making it immediately understandable without unnecessary elaboration.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't address behavioral aspects like what happens after stopping (e.g., confirmation message, error handling), whether it affects other operations, or any side effects, leaving the agent with insufficient context.

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 tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description appropriately doesn't add parameter details beyond what's needed, earning a baseline score near the top of the scale for this dimension.

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 ('Stop') and the target resource ('the web GUI server'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'start_gui' beyond the obvious opposite action, which prevents a perfect score.

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, prerequisites, or context. It doesn't mention when stopping the GUI is appropriate versus using other tools like 'clear_sessions' or 'delete_session', leaving usage entirely implicit.

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/es6kr/claude-session-manager'

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