Skip to main content
Glama

Fetch a Zeek-extracted file

malcolm_extract_file
Read-only

Retrieve metadata for a Zeek-extracted file from Malcolm's server without downloading the bytes, preventing exposure to malware. Ideal after a file scan to verify file integrity via sha256.

Instructions

Fetch one Zeek-extracted file from Malcolm's extracted-files server; returns METADATA ONLY.

    Use this after malcolm_file_scans, which supplies the filename. Use
    arkime_file_by_hash instead when you hold a content hash but no Zeek
    file record, and arkime_session_pcap for a session's packets rather than
    one carved file.

    The bytes never enter the response and nothing is written to disk — a
    carved file may be live malware. The body is streamed against a 100 MB
    cap — under Malcolm's own 128 MB extraction ceiling
    (EXTRACTED_FILE_MAX_BYTES) — and a larger file is refused before it is
    read; url_only=True skips the download without contacting Malcolm at
    all.

    The returned sha256 is computed over the bytes actually served: compare
    it with the malcolm_file_scans row's to see whether the file on disk is
    still the one Zeek recorded. A 404 comes back as found:false — the index
    record outlives the file, which Malcolm prunes. Any other error status is
    reported as a failure, not as a missing file: it says nothing about
    whether the file is on disk.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameYesThe `extracted` value from a malcolm_file_scans row (Zeek's zeek.files.extracted). A full "extracted-files/<name>" URI is accepted too. Names are flat — the extracted-files directory has no subdirectories, so a name carrying a path separator is refused before any request is sent.
url_onlyNoIf true, return only the download URL and skip the download (use for a file larger than the size cap).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Even with readOnlyHint and destructiveHint annotations already present, the description adds crucial behavioral details: bytes never enter the response, nothing is written to disk, the 100 MB streaming cap, refusal of larger files before read, url_only behavior, sha256 computation over served bytes, and the 404 → found:false mapping. This goes well beyond the annotations and helps an agent anticipate edge cases.

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 multi-paragraph but every sentence earns its place. It is front-loaded with the core purpose, followed by usage/alternative guidance, then safety and error semantics. Nothing is redundant, and the structure mirrors how an agent would want to evaluate the tool: what it does, when to use, what to expect.

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 tool's complexity and the existence of an output schema, the description is remarkably complete. It covers the execution chain (after malcolm_file_scans), safety, size limits, stream behavior, hash verification, and the distinction between 404 and other errors. An agent could invoke this tool confidently without further clarification.

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%, and the schema already explains both parameters fully. The description adds relational context: the filename comes from malcolm_file_scans, and url_only is connected to the size cap. Slight extra value over the schema, but not a heavy lift; hence a 4 rather than a baseline 3.

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 opens with a specific verb + resource: 'Fetch one Zeek-extracted file from Malcolm's extracted-files server; returns METADATA ONLY.' This clearly distinguishes the tool from siblings: it returns metadata only, deals with a single carved file, and is tied to Malcolm's server. The explicit contrast with arkime_file_by_hash and arkime_session_pcap reinforces the unique scope.

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 gives explicit usage direction: 'Use this after malcolm_file_scans, which supplies the filename.' It also names alternatives and their exact conditions: 'Use arkime_file_by_hash instead when you hold a content hash but no Zeek file record, and arkime_session_pcap for a session's packets rather than one carved file.' This is textbook when-to-use/when-not-to-use guidance.

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