Skip to main content
Glama
yuriyo

RemoteZip MCP Server

by yuriyo

extract_file

Extract specific files from remote zip archives without downloading the entire archive. Download individual files from zip files hosted online to your local storage.

Instructions

Extract a specific file from a remote zip archive to local storage.

Args:
    url: URL of the remote zip file
    filename: Name of the file to extract
    local_path: Local directory to extract to (default: current directory)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
filenameYes
local_pathNo.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'extract_file' tool, decorated with @mcp.tool() for registration. It extracts a specified file from a remote ZIP archive using RemoteZip and saves it to a local path.
    async def extract_file(url: str, filename: str, local_path: str = ".") -> str:
        """Extract a specific file from a remote zip archive to local storage.
    
        Args:
            url: URL of the remote zip file
            filename: Name of the file to extract
            local_path: Local directory to extract to (default: current directory)
        """
        try:
            with RemoteZip(url) as zip_file:
                zip_file.extract(filename, local_path)
                return f"Extracted {filename} to {local_path}"
        except Exception as e:
            return f"Error extracting file: {str(e)}"
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 mentions the action (extract) and destination (local storage) but lacks details on behavioral traits such as error handling (e.g., if the file doesn't exist in the archive), network timeouts, file overwriting behavior, or security considerations (e.g., handling malicious URLs). This leaves gaps in understanding how the tool behaves beyond the basic operation.

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 appropriately sized and front-loaded, starting with a clear purpose statement followed by a concise parameter list. Every sentence adds value without redundancy, and the structure (purpose then args) is logical and easy to parse.

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 moderate complexity (3 parameters, no annotations, but with an output schema), the description is somewhat complete but has gaps. It covers the purpose and parameters well, but lacks behavioral details (e.g., error handling, side effects). The presence of an output schema means return values are documented elsewhere, but the description could better address operational context like prerequisites or limitations.

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 description coverage is 0%, so the description must compensate. It provides clear semantics for all three parameters: 'url' (URL of the remote zip file), 'filename' (name of the file to extract), and 'local_path' (local directory to extract to with default). This adds meaningful context beyond the schema's basic types, though it could include more details like URL format or path validation.

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 specific action ('Extract a specific file from a remote zip archive to local storage'), including the resource (file from zip archive) and destination (local storage). It distinguishes from sibling tools like 'get_file_info', 'get_zip_statistics', and 'list_files' by focusing on extraction rather than information retrieval or listing.

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 implies usage through its purpose statement but does not explicitly state when to use this tool versus alternatives. For example, it doesn't clarify if this is for single-file extraction versus batch operations or how it differs from potentially similar tools. No explicit exclusions or alternatives 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/yuriyo/remotezip-mcp'

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