Skip to main content
Glama
bx33661

Wireshark MCP

by bx33661
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

wireshark_stats_io_graph

Read-only

Generate a time-based I/O graph of network traffic volume from a pcap file, with optional display filters to split the data.

Instructions

[I/O Graph] Traffic volume by time bucket, optionally split by semicolon-separated display filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filtersNo
intervalNo
pcap_fileYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.0.0
    • addedInput schema / properties / filters
      Added value: +{
+  "default": "",
+  "type": "string"
+}
    • removedInput schema / properties / interval / title
      Removed value: -"Interval"
    • removedInput schema / properties / pcap_file / title
      Removed value: -"Pcap File"
    • removedInput schema / title
      Removed value: -"wireshark_stats_io_graphArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "wireshark_stats_io_graphOutput",
-  "type": "object"
-}New value: +null
  2. Addedv1.2.0
  3. Removedv0.6.4
  4. First observedv0.2.1

TDQS

C2.9/5.0
Behavior3/5

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

The annotations declare readOnlyHint=true and openWorldHint=false, so the safety profile is already covered. The description adds that results are bucketed by time and can be split by semicolon-separated display filters, but it does not describe the return format, aggregation semantics beyond bucketing, or any performance limits.

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?

The description is one compact sentence that front-loads the graph type and main output, with no filler. It is appropriately sized for a brief label, though the extreme brevity contributes to gaps in other dimensions.

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?

For a stats-generation tool with no output schema and three schema parameters at 0% description coverage, the single sentence is insufficient. It does not explain the required pcap_file, the interval parameter, or what the I/O graph result contains.

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 description coverage is 0%, so the description must carry parameter meaning, but it only explains filters as semicolon-separated display filters. It never mentions pcap_file, which is required, or interval, leaving two of three parameters undocumented.

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 resource and output ('I/O Graph', 'Traffic volume by time bucket') and notes optional filter splitting. It distinguishes itself from packet-level siblings and other stats tools by naming the graph type, though it lacks an explicit verb like 'generate' or 'compute'.

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?

There is no guidance on when to choose this tool over siblings such as wireshark_flow_graph, wireshark_stats_endpoints, or wireshark_stats_conversations. Only an implied use for time-bucketed traffic volume is present, with no exclusions, prerequisites, or alternatives named.

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