Skip to main content
Glama
yuriyo

RemoteZip MCP Server

by yuriyo

get_file_info

Retrieve metadata about a specific file within a remote zip archive by providing the archive URL and filename, enabling targeted file inspection without full download.

Instructions

Get information about a specific file in the remote zip archive.

Args:
    url: URL of the remote zip file
    filename: Name of the file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
filenameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'get_file_info' MCP tool. It uses RemoteZip to get file info (size, compressed size) from a remote zip archive given URL and filename.
    @mcp.tool()
    async def get_file_info(url: str, filename: str) -> str:
        """Get information about a specific file in the remote zip archive.
    
        Args:
            url: URL of the remote zip file
            filename: Name of the file
        """
        try:
            with RemoteZip(url) as zip_file:
                info = zip_file.getinfo(filename)
                return f"Filename: {info.filename}\nSize: {info.file_size} bytes\nCompressed size: {info.compress_size} bytes"
        except Exception as e:
            return f"Error getting file info: {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 of behavioral disclosure. It states the tool 'Get information,' implying a read-only operation, but does not disclose any behavioral traits such as error handling, performance characteristics, authentication needs, or rate limits. This leaves significant gaps in understanding how the tool behaves beyond its basic purpose.

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 appropriately sized and front-loaded, with a clear purpose statement followed by parameter details. It avoids unnecessary verbosity, though the 'Args' section could be integrated more seamlessly. Overall, it is efficient with minimal waste.

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 has an output schema (which reduces the need to describe return values in the description) and no annotations, the description covers the basic purpose and parameters. However, it lacks details on behavioral aspects and usage guidelines, making it incomplete for fully understanding the tool's context and operation.

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 description includes an 'Args' section that lists and briefly describes the two parameters ('url' and 'filename'), adding meaning beyond the input schema, which has 0% description coverage. However, it does not provide detailed semantics such as format examples, constraints, or usage context, so it partially compensates for the schema's lack of descriptions but not fully.

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 as 'Get information about a specific file in the remote zip archive,' which includes a specific verb ('Get information') and resource ('specific file in the remote zip archive'). However, it does not explicitly distinguish this tool from its siblings like 'get_zip_statistics' or 'list_files,' which might also provide file-related information, so it lacks sibling differentiation.

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 does not mention when to choose 'get_file_info' over sibling tools such as 'extract_file,' 'get_zip_statistics,' or 'list_files,' nor does it specify any prerequisites or exclusions for usage.

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