Skip to main content
Glama
mako10k

Web Proxy MCP Server

by mako10k

proxy_clear_traffic_log

Clear web proxy traffic logs to remove browsing history and monitoring data, with options for specific domains and confirmation to prevent accidental deletion.

Instructions

Clear the traffic log

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoClear logs for specific domain only
confirmYesConfirmation flag to prevent accidental deletion

Implementation Reference

  • Handler implementation that checks for confirmation flag, calls trafficAnalyzer.clearEntries with optional domain filter, and returns a success message with cleared and remaining entry counts.
    case 'proxy_clear_traffic_log':
      if (!args.confirm) {
        return {
          error: "Confirmation required to clear traffic log",
          isError: true
        };
      }
    
      const cleared = this.trafficAnalyzer.clearEntries(args.domain);
      return {
        content: [{
          type: "text",
          text: `🗑️ Traffic log cleared\nEntries removed: ${cleared}\nRemaining: ${this.trafficAnalyzer.getEntryCount()}`
        }]
      };
  • Tool definition including name, description, and input schema requiring 'confirm' boolean (with optional 'domain' string). Used for validation and listing.
    proxy_clear_traffic_log: {
      name: "proxy_clear_traffic_log",
      description: "Clear the traffic log",
      inputSchema: {
        type: "object",
        properties: {
          domain: {
            type: "string",
            description: "Clear logs for specific domain only"
          },
          confirm: {
            type: "boolean",
            description: "Confirmation flag to prevent accidental deletion",
            default: false
          }
        },
        required: ["confirm"]
      }
    },
  • Core helper method in TrafficAnalyzer class that clears all or domain-specific traffic log entries from memory, resets stats if all cleared, and returns the number of removed entries.
    clearEntries(domain = null) {
      let cleared = 0;
    
      if (domain) {
        const originalLength = this.entries.length;
        this.entries = this.entries.filter(entry => 
          !entry.domain.includes(domain)
        );
        cleared = originalLength - this.entries.length;
      } else {
        cleared = this.entries.length;
        this.entries = [];
        this.stats = {
          totalRequests: 0,
          totalResponseTime: 0,
          domainsTracked: new Set(),
          startTime: new Date()
        };
      }
    
      return cleared;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without disclosing behavioral traits. It does not mention permissions needed, whether the operation is reversible, rate limits, or effects on system performance, which are critical for a destructive operation like clearing logs.

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, direct sentence with zero waste, making it highly concise and front-loaded. It efficiently communicates the core action 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?

Given the tool's destructive nature (clearing logs), no annotations, and no output schema, the description is incomplete. It fails to address safety considerations, error conditions, or what happens post-execution (e.g., confirmation process, system impact), leaving significant gaps for agent understanding.

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?

Schema description coverage is 100%, so the schema fully documents the parameters (domain for filtering, confirm for safety). The description adds no additional meaning beyond what the schema provides, such as explaining parameter interactions or default behaviors, meeting the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Clear the traffic log' states a clear action ('clear') and resource ('traffic log'), which is adequate. However, it lacks specificity about scope (e.g., all logs vs. filtered) and does not differentiate from sibling tools like proxy_get_traffic_log or proxy_analyze_traffic, making it vague in context.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites (e.g., server status), exclusions, or related tools like proxy_get_traffic_log for viewing logs, leaving usage context implied at best.

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