Skip to main content
Glama

Extract file by hash

arkime_file_by_hash
Read-only

Look up a transferred file by its MD5 or SHA256 hash across Arkime sessions. Returns file magic, size, and optional download URL, never the raw bytes.

Instructions

Extract the transferred file matching a content hash across sessions; returns METADATA ONLY.

    Pivots from a file-hash IOC to the actual bytes: Arkime finds the most
    recent session carrying a body with this hash, resolves the capture node,
    and fetches the file. Checks the file-magic and returns metadata (magic,
    size) only — the raw bytes are never put in the MCP response — and
    enforces a size cap, refusing oversized files (use url_only then). Get
    the hash from arkime_session_detail (http.md5 / http.sha256). For the
    whole session's packets rather than one carried file use
    arkime_session_pcap. Returns whether a match was found plus its metadata.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
url_onlyNoIf true, return only the download URL and skip the download.
file_hashYesThe transferred file's content hash: md5 (32 hex chars) or sha256 (64 hex chars). Taken from a session's http.md5 / http.sha256 field (see arkime_session_detail).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations (readOnlyHint=true, destructiveHint=false) already convey safe read. Description adds valuable details: returns metadata only, enforces size cap, finds most recent session, resolves capture node. No contradictions.

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

Conciseness3/5

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

Front-loaded with key summary, but the paragraph is moderately verbose. Mixes overview, workflow details, and caution. Could be more concise while retaining all information.

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

Completeness4/5

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

Given output schema exists (not shown but referenced), description covers tool behavior, limitations (metadata only, size cap), workflow, and usage tips. For a 2-param tool with annotations, it is sufficiently complete.

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

Parameters4/5

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

Schema coverage is 100%. Description adds context beyond schema: file_hash format and source ('md5 or sha256 from arkime_session_detail'), url_only use case (oversized files). Enhances understanding of parameters.

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 states 'Extract the transferred file matching a content hash across sessions; returns METADATA ONLY.' It clearly identifies the action (extract), resource (transferred file), and distinguishing scope (content hash). It also references sibling tools like arkime_session_pcap and arkime_session_detail, differentiating itself.

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 tells when to use alternatives: 'For the whole session's packets... use arkime_session_pcap' and 'refusing oversized files (use url_only then).' Also indicates prerequisite: 'Get the hash from arkime_session_detail.' Provides clear context for selection.

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