Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Descargar el archivo crudo de un recurso

download_resource
Read-only

Download base64-encoded raw bytes from a CKAN resource when preview cannot parse it, specifying the source portal and returning text or JSON up to 5 MB.

Instructions

Raw bytes of a CKAN resource, base64-encoded, for formats the preview can't parse. Max 5 MB. Use format="json"; text only confirms the download.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNotext summary (default) or json structured result.text
sourceNoCKAN portal; nacional (default), cuenca, latacunga or iadb.nacional
resource_idYesThe resource UUID (get it from list_dataset_resources)

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. Changed3 schema fields changedv0.10.0
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / resource_id / description
      Added value: +"The resource UUID (get it from list_dataset_resources)"
    • addedInput schema / properties / source / description
      Added value: +"CKAN portal; nacional (default), cuenca, latacunga or iadb."
  3. Changed5 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / resource_id / title
      Removed value: -"Resource Id"
    • removedInput schema / properties / source / title
      Removed value: -"Source"
    • removedInput schema / title
      Removed value: -"download_resourceArguments"
    • removedOutput schema / title
      Removed value: -"download_resourceDictOutput"
  4. First observedv0.8.12

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint=false, so safety is covered. The description adds genuinely new behavioral facts: output is base64-encoded, hard 5 MB ceiling, and that format='text' only confirms the download rather than returning data.

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?

Three short clauses, front-loaded with what the tool returns, then the size limit, then the format directive. No filler; every sentence 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?

With no output schema, the description carries the return-value burden and does explain the payload (base64 raw bytes) and the size cap. It doesn't describe the shape of the json structured result, a minor remaining gap.

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?

Schema coverage is 100%, so the baseline is 3. The description still adds meaning: it tells the agent that format='json' is required to actually receive the data and that 'text' is only an acknowledgement, which the schema's terse enum description does not convey.

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+resource ('Raw bytes of a CKAN resource') and the delivery format (base64-encoded). It also implicitly distinguishes itself from the preview path by scoping to 'formats the preview can't parse', so an agent can separate it from preview_resource_data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context for use ('for formats the preview can't parse') and a directive on the format param. It doesn't name the alternative sibling (preview_resource_data) explicitly, so it stops short of full when/when-not routing.

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