Skip to main content
Glama

Download session PCAP

arkime_session_pcap
Read-only

Fetch and validate PCAP metadata for Arkime sessions, returning format and size without raw bytes. For large downloads, get a URL instead.

Instructions

Fetch and validate the PCAP for one or more Arkime sessions; returns METADATA ONLY.

    Downloads the raw PCAP bytes, checks the file-magic (pcap/pcapng), and
    returns metadata (magic, format, size) only — never the raw bytes, and
    nothing is persisted to disk. A download over 500 MB is refused before
    a byte is read; url_only=True is the way through, and the way to hand
    the URL to something outside this agent. Needs a session id, which only
    arkime_sessions produces.

    For a session's parsed fields rather than its packets use
    arkime_session_detail; for the bytes that crossed the wire rather than
    the capture container that holds them use arkime_session_payload; and
    for a file this specific session carried use
    arkime_session_file_by_hash, which is more reliable than
    arkime_file_by_hash whenever you already hold a session id.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
url_onlyNoIf true, return only the download URL and skip the download (use for very large sessions).
session_idYesOne Arkime session id, or several comma-separated, each taken from arkime_sessions results (arkime_sessions is the only source of these ids). Several ids are merged into one combined PCAP, and the size ceiling applies to that merged total rather than to each session.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already mark it readOnly and non-destructive, but the description adds substantial behavioral details beyond that: returns metadata only and never raw bytes, nothing is persisted to disk, downloads over 500 MB are refused, and multiple session ids are merged with the size ceiling applied to the total. These are non-obvious traits not present in the annotations.

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 concise and front-loaded: the first sentence immediately delivers the key behavior ('returns METADATA ONLY'), and each subsequent sentence adds essential context (size limit, session id source, sibling distinctions) without redundancy. It earns its length by covering necessary operational details and exclusions.

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?

The description is self-sufficient: it explains return semantics, size limits, url_only bypass, session id provenance, merge behavior, and explicitly differentiates from three related sibling tools. Even without relying on an output schema, an agent has enough context to select and invoke the tool correctly in the appropriate scenario.

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

Parameters5/5

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

Although the schema describes both parameters at 100% coverage, the description adds meaningful semantics not present in the schema: 'Several ids are merged into one combined PCAP, and the size ceiling applies to that merged total rather than to each session' and 'url_only=True is the way through, and the way to hand the URL to something outside this agent.' This enriches understanding beyond the basic property types.

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 starts with 'Fetch and validate the PCAP for one or more Arkime sessions; returns METADATA ONLY,' which is a specific verb+resource statement. It clearly distinguishes the tool from siblings by explicitly contrasting it with arkime_session_detail, arkime_session_payload, and arkime_session_file_by_hash.

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?

It provides direct when-to-use and when-not-to-use guidance, naming alternatives: 'For a session's parsed fields rather than its packets use arkime_session_detail; for the bytes that crossed the wire... use arkime_session_payload.' It also states a prerequisite (session id only from arkime_sessions) and how to handle large sessions via url_only=True.

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