Skip to main content
Glama
mako10k

Web Proxy MCP Server

by mako10k

proxy_export_har

Export HTTP traffic logs in HAR format from the Web Proxy MCP Server for analysis, filtering by domain or time period.

Instructions

Export traffic log as HAR (HTTP Archive) format

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoFilter by specific domain
sinceNoISO timestamp to export entries since
filenameNoOutput filename (without .har extension)

Implementation Reference

  • Tool handler case that invokes trafficAnalyzer.exportHAR with provided arguments and returns formatted success message with export details.
    case 'proxy_export_har':
      const harFile = await this.trafficAnalyzer.exportHAR({
        domain: args.domain,
        since: args.since ? new Date(args.since) : undefined,
        filename: args.filename
      });
    
      return {
        content: [{
          type: "text",
          text: `📁 HAR file exported: ${harFile.filename}\nEntries: ${harFile.entryCount}\nSize: ${harFile.fileSize} bytes`
        }]
      };
  • Tool definition including name, description, and input schema for validation.
    proxy_export_har: {
      name: "proxy_export_har",
      description: "Export traffic log as HAR (HTTP Archive) format",
      inputSchema: {
        type: "object",
        properties: {
          domain: {
            type: "string",
            description: "Filter by specific domain"
          },
          since: {
            type: "string",
            description: "ISO timestamp to export entries since"
          },
          filename: {
            type: "string",
            description: "Output filename (without .har extension)"
          }
        }
      }
    },
  • Implements HAR export: filters traffic entries, converts to HAR 1.2 format using _convertToHAREntry helper, writes JSON file, returns metadata.
    async exportHAR(options = {}) {
      const entries = this.getEntries({
        domain: options.domain,
        since: options.since
      });
    
      const har = {
        log: {
          version: "1.2",
          creator: {
            name: "Web Proxy MCP Server",
            version: "1.0"
          },
          pages: [],
          entries: entries.map(entry => this._convertToHAREntry(entry))
        }
      };
    
      const filename = options.filename ? 
        `${options.filename}.har` : 
        `traffic-${new Date().toISOString().slice(0, 19).replace(/:/g, '-')}.har`;
    
      const filepath = path.resolve(filename);
      const content = JSON.stringify(har, null, 2);
      
      await fs.writeFile(filepath, content);
    
      return {
        filename,
        filepath,
        entryCount: entries.length,
        fileSize: content.length
      };
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool exports data, implying a read-only operation, but doesn't disclose behavioral traits like whether it requires specific permissions, if it's rate-limited, what happens to the exported file (e.g., saved locally or returned as data), or if it affects server state. This is inadequate for a tool with potential side effects like file creation.

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 waste. It is front-loaded with the core action and format, making it easy to scan. Every word earns its place without redundancy.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., a file path, HAR data, or success status), behavioral constraints, or error conditions. For an export tool with three parameters and potential file system interactions, this leaves significant gaps for an AI agent.

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 parameters (domain, since, filename). The description adds no additional meaning beyond implying these are optional filters and output naming, which is already clear from the schema. Baseline 3 is appropriate as 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 action ('Export') and resource ('traffic log') with the specific output format ('HAR (HTTP Archive) format'). It distinguishes from siblings like proxy_get_traffic_log (which likely retrieves but doesn't export) and proxy_export_config (which exports configuration rather than traffic). However, it doesn't explicitly mention what 'traffic log' refers to in this proxy 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 doesn't mention prerequisites (e.g., whether the proxy server must be running or traffic logging enabled), nor does it compare with sibling tools like proxy_get_traffic_log (which might return raw data instead of HAR format) or proxy_analyze_traffic (which might analyze rather than export).

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