Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar encuestas y censos en ANDA

search_anda
Read-only

Search INEC's ANDA catalog of 437+ surveys and censuses, then retrieve survey details via get_anda_survey_info.

Instructions

Search INEC's ANDA catalog of 437+ surveys and censuses; the broadest INEC index. Entries without microdata point to search_inec_estadisticas. Next: get_anda_survey_info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage of results, 1-based (default: 1); see total/total_pages
limitNoResults per page (default: 10, max: 50)
queryNoSearch keywords (e.g. "empleo", "REEM", "censo agropecuario")
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. Changed2 schema fields changedv0.12.0
    • changedInput schema / properties / limit / description
      Previous value: -"Max results (default: 10, max: 50)"New value: +"Results per page (default: 10, max: 50)"
    • addedInput schema / properties / page
      Added value: +{
+  "default": 1,
+  "description": "Page of results, 1-based (default: 1); see total/total_pages",
+  "type": "integer"
+}
  3. Changed3 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 results (default: 10, max: 50)"
    • addedInput schema / properties / query / description
      Added value: +"Search keywords (e.g. \"empleo\", \"REEM\", \"censo agropecuario\")"
  4. Changed5 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"search_andaArguments"
    • removedOutput schema / title
      Removed value: -"search_andaDictOutput"
  5. First observedv0.8.12

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety and openness are covered. The description adds catalog size and the fact that some entries lack microdata, but says nothing about pagination limits, result shape, or rate behavior; with annotations doing the heavy lifting, this is a modest but real addition.

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 dense clauses with zero filler: purpose and scope first, then the disambiguating alternative, then the follow-up tool. Front-loaded and appropriately sized for a list/search tool.

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 four optional parameters, full schema coverage and no output schema, the definition covers what an agent needs to call it and where to go next. It stops short of five only because nothing describes what a result entry looks like or how total/total_pages behave in practice.

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 page, limit, query and format are all documented with defaults, ranges and an example. The description adds no semantics beyond that; a baseline 3 is appropriate when the schema fully carries the parameter burden.

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?

Specific verb (Search) + named resource (INEC's ANDA catalog of 437+ surveys and censuses) plus a scope claim ('the broadest INEC index'). It is clearly distinguishable from the sibling search_inec_estadisticas, which it names, so an agent need not open either schema to tell them apart.

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 onward ('Next: get_anda_survey_info') and gives a disambiguation rule ('Entries without microdata point to search_inec_estadisticas'). However, the rule applies at the result-entry level rather than stating upfront when to pick this search over the other INEC search tools, so no true when-not-to-use guidance is given.

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