Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Descargar microdatos de una encuesta ANDA

download_anda_microdata
Read-only

Get direct download links for Ecuador's ANDA survey microdata ZIP files after accepting research-use terms. Provide the survey idno and check survey info first.

Instructions

Direct links to an ANDA survey's microdata files (accepts ANDA's research-use terms). Check get_anda_survey_info first; returns links to multi-MB ZIPs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idnoYesSurvey idno or numeric id from search_anda (the "idno" or "id" field)
formatNotext summary (default) or json structured result.text

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.12.0
    • changedInput schema / properties / idno / description
      Previous value: -"Survey identifier from search_anda (the \"idno\" field)"New value: +"Survey idno or numeric id from search_anda (the \"idno\" or \"id\" field)"
  3. Changed2 schema fields changedv0.10.0
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / idno / description
      Added value: +"Survey identifier from search_anda (the \"idno\" field)"
  4. Changed4 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / idno / title
      Removed value: -"Idno"
    • removedInput schema / title
      Removed value: -"download_anda_microdataArguments"
    • removedOutput schema / title
      Removed value: -"download_anda_microdataDictOutput"
  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, so the safety profile is covered. The description adds genuinely useful context beyond that: it accepts ANDA's research-use terms, and it returns links to multi-MB ZIPs rather than the data itself, warning about payload size.

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?

Two tight sentences with zero waste, front-loading the return type and following with the prerequisite and size warning. Every clause carries information an agent needs.

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?

No output schema exists, so the description usefully discloses the return shape (links to ZIPs) and the research-use terms constraint. It is essentially complete for a two-parameter link tool, though it could say more about how to consume the links.

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 both idno and format are already documented in the schema; baseline is 3. The description implies the idno comes from an ANDA survey but adds no syntax or format detail beyond the schema.

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 the resource (an ANDA survey's microdata files) and the outcome (direct links, multi-MB ZIPs), and implicitly distinguishes from the metadata sibling get_anda_survey_info. The action verb is somewhat implicit ('direct links to') rather than an explicit 'download', so it lands just short of a 5.

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?

Explicitly routes the agent through a prerequisite: 'Check get_anda_survey_info first', which is actionable sequencing with a named sibling. It lacks explicit exclusions (when NOT to use vs download_resource), so it stops short of a 5.

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