Skip to main content
Glama
mako10k

Web Proxy MCP Server

by mako10k

proxy_stop_server

Stop the HTTP/HTTPS proxy server to halt automated traffic monitoring and analysis operations.

Instructions

Stop the proxy server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler implementation for the 'proxy_stop_server' tool. It checks if the proxy server is running, stops it by calling proxyServer.stop(), and returns an appropriate success or status message.
    case 'proxy_stop_server':
      if (!this.proxyServer.isRunning()) {
        return {
          content: [{
            type: "text",
            text: "Proxy server is not running"
          }]
        };
      }
    
      await this.proxyServer.stop();
      return {
        content: [{
          type: "text",
          text: "✅ Proxy server stopped"
        }]
      };
  • Schema definition for the proxy_stop_server tool, specifying its name, description, and empty input schema (no parameters required).
    proxy_stop_server: {
      name: "proxy_stop_server",
      description: "Stop the proxy server",
      inputSchema: {
        type: "object",
        properties: {}
      }
    },
  • index.js:65-73 (registration)
    MCP server registration for listing all tools, including proxy_stop_server, using the TOOLS object from tool-definitions.js.
    // List available tools
    this.server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: Object.entries(TOOLS).map(([name, tool]) => ({
          name,
          description: tool.description,
          inputSchema: tool.inputSchema
        }))
      };
  • index.js:77-98 (registration)
    MCP server registration for handling tool calls, dispatching to ToolHandlers.handleTool which routes to the specific proxy_stop_server handler.
    this.server.setRequestHandler(CallToolRequestSchema, async (request) => {
      const { name, arguments: args } = request.params;
    
      try {
        const result = await this.toolHandlers.handleTool(name, args || {});
    
        if (result.isError) {
          throw new McpError(
            ErrorCode.InternalError,
            result.error
          );
        }
    
        return result;
    
      } catch (error) {
        console.error(`Tool error [${name}]:`, error.message);
        throw new McpError(
          ErrorCode.InternalError,
          `Tool execution failed: ${error.message}`
        );
      }
  • Core implementation of the proxy server stop method (ProxyServerWithSSL.stop()), called by the tool handler to gracefully close the HTTP server.
    async stop() {
      if (!this.running || !this.server) {
        return;
      }
    
      return new Promise((resolve) => {
        this.server.close(() => {
          this.running = false;
          this.server = null;
          console.log('✅ Proxy server stopped');
          resolve();
        });
      });
    }
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. 'Stop the proxy server' implies a destructive/mutating operation, but it doesn't specify consequences (e.g., terminates active connections, affects other tools), permissions required, error conditions (e.g., if server isn't running), or rate limits. For a mutation tool with zero annotation coverage, this is inadequate.

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 ('Stop') and resource ('proxy server'), making it immediately scannable and understandable. Every word earns its place.

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?

Given the tool's complexity (a server control operation), lack of annotations, and no output schema, the description is insufficient. It doesn't explain what 'stopping' entails behaviorally, what happens to active sessions, whether it's reversible, or what the response looks like. For a mutation tool in a proxy management context, more detail is needed.

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 absence of inputs. The description doesn't need to add parameter information, and it doesn't contradict the schema. A baseline of 4 is appropriate for zero-parameter tools where the schema handles documentation.

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 resource ('the proxy server'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'proxy_start_server' or 'proxy_server_status', but the verb 'Stop' inherently contrasts with 'Start' and 'Status', providing some implicit differentiation. A 5 would require explicit sibling comparison.

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., server must be running), exclusions (e.g., don't use if server is already stopped), or relationships to sibling tools like 'proxy_start_server' or 'proxy_server_status'. The agent must infer usage from context alone.

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/mako10k/mcp-web-proxy'

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