Skip to main content
Glama
mako10k

Web Proxy MCP Server

by mako10k

proxy_server_status

Check proxy server status and statistics including SSL bumping status to monitor traffic and analyze performance.

Instructions

Get proxy server status and statistics including SSL bumping status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler implementation that fetches proxy server status, target stats, and traffic count, returning formatted JSON status.
    case 'proxy_server_status':
      const status = this.proxyServer.getStatus();
      const stats = this.targetManager.getStats();
      
      return {
        content: [{
          type: "text",
          text: `📊 Proxy Server Status\n\n${JSON.stringify({
            ...status,
            targetStats: stats,
            trafficEntries: this.trafficAnalyzer ? this.trafficAnalyzer.getEntryCount() : 0
          }, null, 2)}`
        }]
      };
  • Tool definition including name, description, and empty input schema.
    proxy_server_status: {
      name: "proxy_server_status",
      description: "Get proxy server status and statistics including SSL bumping status",
      inputSchema: {
        type: "object",
        properties: {}
      }
    },
  • index.js:66-74 (registration)
    Registers all tools including proxy_server_status in MCP ListTools handler using TOOLS export.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: Object.entries(TOOLS).map(([name, tool]) => ({
          name,
          description: tool.description,
          inputSchema: tool.inputSchema
        }))
      };
    });
  • index.js:81-82 (registration)
    Routes tool calls to ToolHandlers.handleTool which dispatches to proxy_server_status case.
    const result = await this.toolHandlers.handleTool(name, args || {});
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 mentions what information is returned (status, statistics, SSL bumping status) but doesn't describe format, real-time vs cached data, permission requirements, or error conditions. For a status-checking tool with zero annotation coverage, this leaves significant gaps.

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 that communicates the core purpose without unnecessary words. Every element ('Get proxy server status and statistics including SSL bumping status') serves a clear informational purpose.

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 simplicity (0 parameters, no output schema) and lack of annotations, the description provides basic purpose but lacks details about return format, data freshness, or error handling. It's minimally adequate but could benefit from more behavioral context for a status-checking operation.

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 baseline is 4. The description doesn't need to explain parameters, and it correctly indicates this is a parameterless status query.

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 with a specific verb ('Get') and resource ('proxy server status and statistics'), including the specific detail about SSL bumping status. It distinguishes itself from siblings like proxy_get_performance_metrics or proxy_get_traffic_log by focusing on overall server status rather than specific metrics or logs.

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 implies usage for checking server status and SSL bumping, but doesn't explicitly state when to use this tool versus alternatives like proxy_get_performance_metrics or proxy_start_server. No guidance on prerequisites, frequency, or exclusions is provided.

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