Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Listar el contenido de un archivo ZIP

list_zip_contents
Read-only

List files and sizes inside a remote ZIP archive over HTTP without downloading the whole file. Supports large archives and pagination.

Instructions

List a remote ZIP's members (name, size) via HTTP Range requests, without downloading it; works for archives far beyond 5 MB. No ZIP64.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesDirect URL to a .zip file (from another tool's result, e.g. get_inec_publicacion_archivos, search_archivos(fuente="censo")).
limitNoMax members returned (default 200, max 1000).
formatNotext summary (default) or json structured result.text
offsetNoPagination offset over the member list.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.10.0
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / limit / description
      Added value: +"Max members returned (default 200, max 1000)."
    • addedInput schema / properties / offset / description
      Added value: +"Pagination offset over the member list."
    • addedInput schema / properties / url / description
      Added value: +"Direct URL to a .zip file (from another tool's result, e.g. get_inec_publicacion_archivos, search_archivos(fuente=\"censo\"))."
  2. Changed6 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / offset / title
      Removed value: -"Offset"
    • removedInput schema / properties / url / title
      Removed value: -"Url"
    • removedInput schema / title
      Removed value: -"list_zip_contentsArguments"
    • removedOutput schema / title
      Removed value: -"list_zip_contentsDictOutput"
  3. First observedv0.8.12

TDQS

A3.8/5.0
Behavior4/5

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

With readOnlyHint/openWorldHint already covering the safety profile, the description adds real behavioral context: it uses HTTP Range requests, avoids a full download, scales past 5 MB, and discloses a limitation ('No ZIP64'). The limitation note is exactly the kind of trait annotations cannot convey.

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?

A single tight sentence front-loads verb and resource, then attaches mechanism, capability, and limitation with no filler. Every clause carries information.

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

Completeness4/5

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

An output schema exists, so return-value detail like '(name, size)' is redundant but harmless, and the safety semantics are covered by annotations. The description supplies the mechanism and the ZIP64 caveat, leaving little an agent would need to call this correctly.

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?

Schema description coverage is 100%, so url, limit, format, and offset are already documented in the schema. The description adds no parameter syntax or format detail beyond what is present, so the baseline 3 applies.

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?

States a specific verb and resource ('List a remote ZIP's members') with the returned fields (name, size) called out. It does not explicitly differentiate itself from siblings like download_resource, but the tool's purpose is unambiguous.

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 phrase 'without downloading it' implies the intended scenario (inspecting a remote archive cheaply), which gives usable context. However, it never names download_resource or another alternative, nor states when this tool is the wrong choice, so guidance remains implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools