Skip to main content
Glama
yuriyo

RemoteZip MCP Server

by yuriyo

get_zip_statistics

Analyze remote ZIP archive statistics to understand file counts, sizes, and structure without downloading the entire archive.

Instructions

Get statistics about the remote zip archive.

Args:
    url: URL of the remote zip file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'get_zip_statistics' tool. It uses RemoteZip to access the zip archive at the given URL, retrieves the file info list, calculates total number of files, total uncompressed size, and total compressed size, then returns a formatted string with these statistics. Includes error handling.
    @mcp.tool()
    async def get_zip_statistics(url: str) -> str:
        """Get statistics about the remote zip archive.
    
        Args:
            url: URL of the remote zip file
        """
        try:
            with RemoteZip(url) as zip_file:
                files = zip_file.infolist()
                total_files = len(files)
                total_size = sum(info.file_size for info in files)
                total_compressed = sum(info.compress_size for info in files)
                return f"Total files: {total_files}\nTotal uncompressed size: {total_size} bytes\nTotal compressed size: {total_compressed} bytes"
        except Exception as e:
            return f"Error getting statistics: {str(e)}"
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 that it gets statistics about a 'remote' zip archive from a URL, implying network access, but doesn't cover critical aspects like error handling, performance implications, authentication needs, or rate limits. This leaves significant gaps for an agent to understand the tool's behavior fully.

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 main purpose stated clearly in the first sentence. The second sentence provides parameter information without unnecessary elaboration, making it efficient. However, it could be slightly improved by integrating the parameter details more seamlessly.

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 (one parameter, no annotations, but with an output schema), the description is somewhat complete but has gaps. It explains the basic purpose and parameter, but lacks usage guidelines and behavioral details. The presence of an output schema means return values are documented elsewhere, reducing the burden on the description, but overall it's only adequate for minimal understanding.

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 adds minimal semantics by specifying that the 'url' parameter is for a 'remote zip file', which clarifies its purpose beyond the schema's generic 'Url' title. However, with 0% schema description coverage and only one parameter, this provides some value but doesn't fully compensate for the lack of detailed schema documentation, such as URL format requirements or constraints.

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 verb 'Get' and the resource 'statistics about the remote zip archive', making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_file_info' or 'list_files', which might also provide information about files/archives.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_file_info' or 'list_files'. The description only states what it does, without indicating specific contexts, prerequisites, or exclusions for its use.

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