Wireshark-MCP

Overview Schema Source Related Servers Discussions Admin

generate_timeline

Generate a chronological timeline of network events from a loaded PCAP, grouping occurrences by specified time intervals to support forensic analysis and threat hunting.

Instructions

Generate a timeline of network events from the loaded PCAP.

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": {
      "session_id": "<session_id>"
    },
    "name": "generate_timeline"
  }
}

Input Schema

Name	Required	Description	Default
`session_id`	Yes	ID of the session
`interval_seconds`	No	Time interval in seconds for grouping events

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 9, 2026

TDQS

B3.1/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. It only states the basic action and the prerequisite of a loaded PCAP, but does not disclose output format, potential side effects, error behavior, or any other behavioral traits beyond what the name implies.

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 concise sentence that front-loads the core action and object. Every word contributes; there is no redundancy or filler.

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?

For a tool with two parameters and no output schema, the description is minimal but somewhat adequate. It fails to explain the output format or provide usage context, but the name and description give a basic understanding. The lack of any behavioral or return-value detail leaves gaps.

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% (both session_id and interval_seconds have descriptions), so the schema already documents parameter semantics. The tool description does not add any additional parameter meaning, meriting the baseline score of 3.

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 ('Generate') and the resource ('a timeline of network events from the loaded PCAP'), making its purpose understandable. However, it does not differentiate from similar timing/analysis tools in the sibling list like 'analyze_timing' or 'summary_stats'.

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, nor any exclusions or prerequisites beyond the implicit 'loaded PCAP' context. There is no mention of scenario fit or comparison with sibling tools.

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