Skip to main content
Glama
mako10k

Web Proxy MCP Server

by mako10k

proxy_get_performance_metrics

Retrieve proxy server performance metrics to monitor traffic, analyze data, and manage browser setup. Optionally reset metrics after collection.

Instructions

Get proxy server performance metrics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
resetNoReset metrics after retrieval

Implementation Reference

  • Handler logic retrieves performance metrics from proxyServer, optionally resets them, and returns formatted text response.
    case 'proxy_get_performance_metrics':
      const metrics = this.proxyServer.getMetrics();
      if (args.reset) {
        this.proxyServer.resetMetrics();
      }
    
      return {
        content: [{
          type: "text",
          text: `⚡ Performance Metrics\n\n${JSON.stringify(metrics, null, 2)}${args.reset ? '\n\n✅ Metrics reset' : ''}`
        }]
      };
  • Tool definition including name, description, and input schema with optional 'reset' boolean parameter.
    proxy_get_performance_metrics: {
      name: "proxy_get_performance_metrics",
      description: "Get proxy server performance metrics",
      inputSchema: {
        type: "object",
        properties: {
          reset: {
            type: "boolean",
            description: "Reset metrics after retrieval",
            default: false
          }
        }
      }
    }
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. It states 'Get' implies a read operation, but doesn't mention if this requires specific permissions, how metrics are formatted, whether it's real-time or historical, or any rate limits. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy to understand at a glance.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what metrics are returned, their format, or any behavioral nuances like permissions or data freshness. For a performance metrics tool with no structured context, this description is too minimal to be fully helpful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with one parameter 'reset' fully documented in the schema. The description doesn't add any meaning beyond the schema, such as explaining what metrics are included or how resetting affects them. Baseline score of 3 is appropriate since the schema does the heavy lifting.

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 verb 'Get' and the resource 'proxy server performance metrics', making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'proxy_server_status' or 'proxy_analyze_traffic', which might have overlapping functionality, so it doesn't reach the highest 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. With siblings like 'proxy_server_status' and 'proxy_analyze_traffic' that might relate to performance or metrics, there's no indication of context, exclusions, or prerequisites for usage.

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