Skip to main content
Glama
yuriyo

RemoteZip MCP Server

by yuriyo

list_files

List files inside remote zip archives from HTTP, HTTPS, or FTP URLs without downloading the entire archive.

Instructions

Get list of files in a remote zip archive.

Args:
    url: URL of the remote zip file (http, https, ftp supported)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'list_files' tool, decorated with @mcp.tool() for registration. It takes a URL to a remote zip file, uses RemoteZip to list the files, joins them with newlines, and returns the list or an error message.
    @mcp.tool()
    async def list_files(url: str) -> str:
        """Get list of files in a remote zip archive.
    
        Args:
            url: URL of the remote zip file (http, https, ftp supported)
        """
        try:
            with RemoteZip(url) as zip_file:
                files = zip_file.namelist()
                return "\n".join(files)
        except Exception as e:
            return f"Error listing files: {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 mentions the tool reads from remote zip archives via supported protocols (http, https, ftp), which is useful context. However, it doesn't describe critical behaviors like error handling, performance characteristics, authentication needs, or what the output contains beyond 'list of files.' For a tool with no annotations, this leaves significant gaps.

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. The first sentence clearly states the purpose, followed by a brief 'Args' section that efficiently explains the parameter. There is no wasted text, and every sentence adds value to understanding the tool.

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 partially complete. It covers the purpose and parameter semantics adequately. However, it lacks behavioral details and usage guidelines. The presence of an output schema means the description doesn't need to explain return values, but other contextual gaps remain.

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 description adds meaningful semantics beyond the input schema. The schema only indicates a required 'url' parameter of type string. The description clarifies that this is 'URL of the remote zip file (http, https, ftp supported),' specifying the expected format and supported protocols. With 0% schema description coverage, this compensates well for the single parameter.

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: 'Get list of files in a remote zip archive.' It specifies the verb ('Get list') and resource ('files in a remote zip archive'), making the function unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_zip_statistics' or 'get_file_info', which might also provide file-related information.

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 doesn't mention sibling tools like 'extract_file' or 'get_file_info', nor does it specify scenarios where listing files is preferred over other operations. Usage context is implied but not explicitly stated.

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