Skip to main content
Glama
yfe404

proxy-mcp

by yfe404
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

proxy_list_traffic

Retrieve captured HTTP exchanges, applying filters by URL, method, status, or hostname, with pagination support.

Instructions

List captured HTTP exchanges with optional filters. Returns paginated results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax entries to return (default: 50)
offsetNoSkip first N entries (default: 0)
url_filterNoFilter by URL substring
method_filterNoFilter by HTTP method (e.g., GET, POST)
status_filterNoFilter by response status code
hostname_filterNoFilter by hostname substring

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.5.3
    • removedInput schema / properties / source_filter
      Removed value: -{
-  "description": "Filter by traffic source: 'explicit' (proxy-configured) or 'transparent' (iptables-redirected)",
-  "enum": [
-    "explicit",
-    "transparent"
-  ],
-  "type": "string"
-}
  2. Changed1 schema field changedv2.3.0
    • addedInput schema / properties / source_filter
      Added value: +{
+  "description": "Filter by traffic source: 'explicit' (proxy-configured) or 'transparent' (iptables-redirected)",
+  "enum": [
+    "explicit",
+    "transparent"
+  ],
+  "type": "string"
+}
  3. Addedv1.0.0

TDQS

B3.1/5.0
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 mentions 'Returns paginated results,' which is useful context about output behavior. However, it doesn't describe important aspects like whether this is a read-only operation, what permissions are required, rate limits, or what happens if no exchanges are captured. For a tool with no 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 extremely concise with just two sentences: 'List captured HTTP exchanges with optional filters. Returns paginated results.' Every word earns its place—the first sentence states the core purpose, and the second adds critical behavioral context. It's front-loaded with the main action and wastes no space.

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 moderate complexity (6 parameters, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose and pagination behavior but lacks details on error conditions, output format, or integration with sibling tools. Without annotations or output schema, the agent must infer much from the parameter schema alone.

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 all 6 parameters with clear descriptions. The description adds minimal value beyond the schema by mentioning 'optional filters' generically, but doesn't provide additional context about parameter interactions, default behaviors beyond the schema, or usage examples. This meets the baseline for high schema coverage.

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: 'List captured HTTP exchanges with optional filters.' This specifies the verb ('List'), resource ('captured HTTP exchanges'), and scope ('with optional filters'). However, it doesn't explicitly differentiate from sibling tools like 'proxy_search_traffic' or 'proxy_get_exchange', which appear related but have different functions.

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 mentions 'optional filters' but doesn't clarify when filtering is appropriate or when other tools like 'proxy_search_traffic' might be better suited. There's no mention of prerequisites, dependencies, or typical use cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools