Skip to main content
Glama

Extract file by hash

arkime_file_by_hash
Read-only

Check captured sessions for a transferred file matching a provided MD5 or SHA256 content hash; returns metadata (type, size) only and an optional download URL for forensic review.

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. That "most recent" is the catch — when the same
    file moved several times, this answers about the last transfer, which is
    usually not the one under investigation. Use this to find out whether a
    known-bad hash appeared at all, and arkime_session_file_by_hash to pin
    the answer to a session you already hold — a "no match" here is not
    proof the file is absent, since measured on Malcolm v26.07.1 that route served
    a body this one declined. Checks the file-magic and returns metadata
    (magic, size) only — the raw bytes are never put in the MCP response —
    and refuses a file over 100 MB before reading it (use url_only then).
    The hash comes from a session's http.md5 / http.sha256, which
    malcolm_search returns. 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, which malcolm_search returns and arkime_session_detail does not (measured on Malcolm v26.07.1).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Install Server

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/destructive annotations, the description discloses key behavioral traits: the 'most recent session' selection caveat, that raw bytes are never placed in the MCP response, the 100 MB refusal, and that a 'no match' is not proof of absence. It also includes version-specific measurement context, adding significant transparency.

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 front-loaded with the core purpose and then lists caveats, but it is somewhat verbose with multiple clauses and version-specific asides. Every sentence adds information, though a tighter structure would improve readability without losing value.

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?

Given the output schema exists and the tool has moderate complexity, the description adequately covers all needed aspects: return type (metadata only), important limitations (most-recent, no-match caveat), file size limit, and alternatives. No critical operational detail is missing.

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%, but the description supplements parameter meaning by specifying hash formats (md5/sha256), source fields (http.md5/http.sha256), and how they relate to malcolm_search vs arkime_session_detail. It also clarifies url_only's role in the large-file case, going beyond the schema's basic descriptions.

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 the action ('Extract the transferred file matching a content hash across sessions') and the output scope ('returns METADATA ONLY'). It also distinguishes itself from the sibling 'arkime_session_file_by_hash' by noting the session-scoped alternative, making the purpose unambiguous.

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?

The description provides explicit usage guidance: 'Use this to find out whether a known-bad hash appeared at all' and directly names the alternative tool for pinning to a session. It also advises using url_only for >100 MB files and points to arkime_session_pcap for entire packets, offering clear when-to-use and when-not-to-use context.

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

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