Skip to main content
Glama

List indexed PCAP files

arkime_pcap_files
Read-only

Discover what PCAP files are indexed, including file size, session count, and time span, to verify capture coverage and identify gaps.

Instructions

List the PCAP files Arkime has indexed, with each file's coverage.

    Use this to answer "what capture do we actually hold" — which files
    exist, how big they are, how many sessions each carries and the time
    span it covers. That is the file-level view; for the dataset-level view
    (how fresh each sensor is, how many documents per log type) use
    malcolm_data_coverage, and to search the sessions themselves use
    arkime_sessions.

    On one node, an interval between a file's last packet and the next
    file's first is an interval with no captured packets, and no search can
    tell you whether the link was quiet or the capture was down — this list
    is the only place that distinction shows up. Files from different nodes
    overlap in time, so compare within a node. Per-file fields and their
    units are in the output schema.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax files to return.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations declare readOnlyHint=true and destructiveHint=false; the description adds context about intervals with no captured packets and warns that different nodes overlap in time, which is valuable for interpretation.

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 structured into three focused paragraphs: purpose, usage, and behavior, with no redundant sentences. It's appropriately sized for the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only list tool with one parameter, the description covers purpose, differentiation, and a key analytical insight. The presence of an output schema means return values don't need to be explained.

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 coverage is 100% with a single optional `limit` parameter described as 'Max files to return.' The description doesn't add parameter-specific semantics but points to the output schema for per-file field units, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'List the PCAP files Arkime has indexed, with each file's coverage,' specifying the verb, resource, and scope. It also differentiates from siblings by calling it the 'file-level view' versus malcolm_data_coverage and arkime_sessions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use this to answer...' and provides alternatives: 'for the dataset-level view... use malcolm_data_coverage, and to search the sessions themselves use arkime_sessions.' Also gives nuanced guidance about gap detection and node comparisons.

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/nagameTW/mcp-server-malcolm'

If you have feedback or need assistance with the MCP directory API, please join our Discord server