Charles MCP Server

Overview Schema Source Related Servers Discussions Admin

get_capture_analysis_stats

Analyze network traffic from live captures or saved recordings to provide coarse traffic class counts, helping identify patterns and issues in API calls, HTTP requests, or errors.

Instructions

Return coarse traffic class counts for a live capture or saved recording.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "source": "<source>"
    },
    "name": "get_capture_analysis_stats"
  }
}

Input Schema

Name	Required	Default
`source`	Yes
`capture_id`	No
`recording_path`	No
`preset`	No	api_focus
`scan_limit`	No

Output Schema

Name	Required	Description	Default
`preset`	Yes
`source`	Yes
`warnings`	No
`total_items`	No
`scanned_count`	No
`classified_counts`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.1Mar 26, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'coarse' hints at granularity limitations, the description omits critical behavioral details: what the 'scan_limit' parameter controls, the computational cost of analysis, whether presets filter input or output, and any side effects on the capture state.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence of 10 words that efficiently conveys the core function. Front-loaded with the action verb 'Return'. However, given the tool complexity (5 parameters with 0% schema coverage), this brevity constitutes under-documentation rather than effective conciseness.

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?

Despite having an output schema (reducing the need to describe return values), the description is inadequate for a tool with 5 parameters and complex input logic. Missing: clarification of parameter relationships (capture_id vs recording_path), enumeration semantics for 'preset', and behavioral constraints. Requires significant inference from parameter names alone.

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

Parameters2/5

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

Schema coverage is 0%, requiring the description to compensate for 5 undocumented parameters. While 'live capture or saved recording' hints at the domain for 'capture_id' and 'recording_path', it fails to explain the required 'source' parameter, the enum values for 'preset' (api_focus, errors_only, etc.), or the purpose of 'scan_limit'. Insufficient compensation for zero schema documentation.

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 states a specific action ('Return') and resource ('traffic class counts') with clear scope ('live capture or saved recording'). The qualifier 'coarse' provides useful granularity context. However, it doesn't explicitly distinguish when to use this versus sibling tools like 'analyze_recorded_traffic' or 'group_capture_analysis'.

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 provided on when to use this tool versus alternatives like 'query_recorded_traffic' or 'get_recording_snapshot'. Critically missing: explanation of the relationship between 'capture_id' and 'recording_path' parameters (mutually exclusive? complementary?) and when each should be used.

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

Deploy Server