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 names and sizes of files in a remote ZIP archive via HTTP Range requests to inspect its contents without downloading the full file.

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.13.0
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  2. Changed1 schema field changedv0.11.0
    • changedInput schema / properties / url / description
      Previous value: -"Direct URL to a .zip file (from another tool's result, e.g. get_inec_publicacion_archivos, search_archivos(fuente=\"censo\"))."New value: +"Direct URL to a .zip file (from another tool's result, e.g. get_inec_publicacion_archivos, search_archivos(fuente='censo'))."
  3. 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\"))."
  4. 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"
  5. First observedv0.8.12

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, but the description adds real behavioral context: it works over HTTP Range requests without downloading the archive, handles archives well beyond 5 MB, and explicitly does not support ZIP64. That limitation disclosure is exactly the kind of trait annotations cannot express.

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 front-loaded sentence delivering mechanism, return shape, and the size/ZIP64 caveats with zero filler. Nothing to trim.

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?

For a 4-param read-only tool with no output schema, the description covers the operation, the return fields, and the key scale/ZIP64 constraints. Pagination behavior (limit/offset) is only covered by the schema, which is acceptable but leaves a small gap.

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% and all four parameters are documented there, including the URL provenance hint. The description adds no parameter-level meaning beyond what the schema already carries, so the baseline 3 applies.

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?

States a specific verb (list), resource (remote ZIP members), and even the mechanism (HTTP Range requests) plus the returned fields (name, size). No sibling tool lists ZIP contents, so it is trivially distinguishable from the rest of the catalog.

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 context ('without downloading it', 'works for archives far beyond 5 MB') which helps an agent decide to call it for large remote archives, but it never states when not to use it or names an alternative (e.g. download_resource). Usage is inferable, not 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