Skip to main content
Glama

download_file

Retrieve files from the Kali Linux container to access scan results, output files, and security tool data for analysis and reporting.

Instructions

Read/download a file from the Kali Linux container. Useful for retrieving scan results and output files.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute path of the file inside the container

Implementation Reference

  • The "download_file" tool registration and handler implementation using docker.readFile.
    server.tool(
      "download_file",
      "Read/download a file from the Kali Linux container. Useful for retrieving scan results and output files.",
      {
        path: z.string().describe("Absolute path of the file inside the container"),
      },
      async ({ path }) => {
        try {
          const content = await docker.readFile(path);
          return {
            content: [{ type: "text", text: content }],
          };
        } catch (err) {
          return {
            content: [
              {
                type: "text",
                text: `Failed to download file: ${err instanceof Error ? err.message : String(err)}`,
              },
            ],
            isError: true,
          };
        }
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the tool reads/downloads files, implying a read-only operation, but doesn't specify critical details like file size limits, supported formats, error handling (e.g., if the path doesn't exist), or how the file is returned (e.g., as binary data, base64). This leaves significant gaps for an agent to use it safely and effectively.

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 concise and front-loaded with the core purpose in the first sentence. The second sentence adds useful context without redundancy. However, it could be slightly more structured by explicitly separating purpose from usage examples, but overall, it's efficient with minimal waste.

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

Completeness2/5

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

Given the tool's complexity (file retrieval from a container), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., file content, download link, or metadata), potential side effects, or error conditions. For a tool that interacts with a container filesystem, more context on permissions, paths, and output handling is needed for effective use.

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

Parameters3/5

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

The input schema has 100% description coverage, with the 'path' parameter clearly documented as 'Absolute path of the file inside the container.' The description adds no additional parameter semantics beyond what the schema provides, such as examples or constraints. Since schema coverage is high, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 action ('Read/download') and target resource ('a file from the Kali Linux container'), making the purpose immediately understandable. It distinguishes from siblings like 'upload_file' (opposite direction) and 'list_files' (metadata vs content retrieval). However, it doesn't explicitly differentiate from 'execute_command' which might also produce files, leaving some ambiguity.

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

Usage Guidelines3/5

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

The description provides implied usage context with 'Useful for retrieving scan results and output files,' suggesting typical scenarios. However, it lacks explicit guidance on when to use this versus alternatives like 'list_files' (for browsing) or 'execute_command' (for generating files first). No clear exclusions or prerequisites are mentioned.

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/Hannes221/kali-mcp'

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