Skip to main content
Glama
threat-zone

Threat.Zone MCP Server

by threat-zone

download_sanitized_file

Download Content Disarm and Reconstruction (CDR) sanitized files from malware analysis submissions to access safe versions of potentially malicious content.

Instructions

Download the CDR-sanitized file for a given submission UUID.

Args: uuid: Submission UUID

Returns: Base64-encoded file content

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'download_sanitized_file' tool, which is also registered via the @app.tool decorator. It downloads the CDR-sanitized version of the analyzed file from the Threat.Zone API endpoint and returns the content as a base64-encoded string.
    @app.tool
    async def download_sanitized_file(uuid: str) -> str:
        """
        Download the CDR-sanitized file for a given submission UUID.
        
        Args:
            uuid: Submission UUID
            
        Returns:
            Base64-encoded file content
        """
        import base64
        content = await get_client().download(f"/public-api/download/cdr/{uuid}")
        return base64.b64encode(content).decode('utf-8')
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool downloads a file and returns base64-encoded content, which is basic behavioral info. However, it lacks details on permissions, rate limits, file size constraints, or error handling. For a download operation without annotations, this is insufficient to ensure safe and effective use.

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 highly concise and well-structured: a clear purpose statement followed by brief 'Args' and 'Returns' sections. Every sentence adds value without redundancy, making it easy to parse quickly. The front-loaded purpose statement ensures immediate understanding.

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

Completeness3/5

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

Given the tool's simplicity (one parameter) and the presence of an output schema (implied by 'Returns' statement), the description is minimally adequate. However, with no annotations and multiple sibling tools, it lacks context on behavioral risks and alternatives. For a download operation, more detail on constraints or integration would improve completeness.

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?

The input schema has 0% description coverage, but the tool has only one parameter. The description adds meaningful context by specifying that 'uuid' refers to a 'Submission UUID', clarifying its purpose beyond the schema's generic 'Uuid' title. This compensates well for the low schema coverage, though it doesn't detail format or validation rules.

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

Purpose4/5

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

The description clearly states the tool's purpose: 'Download the CDR-sanitized file for a given submission UUID.' It specifies the verb (download), resource (CDR-sanitized file), and key input (submission UUID). However, it doesn't explicitly differentiate from sibling tools like 'download_html_report' or 'get_submission_artifacts', which might offer alternative file retrieval methods.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It mentions the required UUID but doesn't explain prerequisites, such as whether the submission must be complete or accessible. With siblings like 'download_html_report' and various 'get_submission_*' tools, the lack of comparative context leaves usage unclear.

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/threat-zone/threatzonemcp'

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