Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar bases mensuales de infoMIES

search_infomies_bases_mensuales
Read-only

Search and retrieve infoMIES monthly program databases for economic inclusion (anc) or social inclusion (is). Filter by year or query to find specific files.

Instructions

infoMIES monthly program databases, serie "anc" (economic inclusion) or "is" (social inclusion). Closed years have one year-end file. .rar files: links only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
anioNoSpecific year to fetch, e.g. 2024.
queryNoFree text matched (accent-insensitive) against the file's label, year, or URL, e.g. "julio", "2023".
serieYes"anc" or "is".
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. Changed4 schema fields changedv0.10.0
    • addedInput schema / properties / anio / description
      Added value: +"Specific year to fetch, e.g. 2024."
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / query / description
      Added value: +"Free text matched (accent-insensitive) against the file's label, year, or URL, e.g. \"julio\", \"2023\"."
    • addedInput schema / properties / serie / description
      Added value: +"\"anc\" or \"is\"."
  3. Changed6 schema fields changedv0.8.14
    • removedInput schema / properties / anio / title
      Removed value: -"Anio"
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / properties / serie / title
      Removed value: -"Serie"
    • removedInput schema / title
      Removed value: -"search_infomies_bases_mensualesArguments"
    • removedOutput schema / title
      Removed value: -"search_infomies_bases_mensualesDictOutput"
  4. First observedv0.8.12

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral notes ('closed years have one year-end file', '.rar files: links only'), but does not describe pagination or return format beyond that, so a baseline-plus score is appropriate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very short and front-loads the resource, then the series and file behavior. Slightly telegraphic fragments ('.rar files: links only.') but every clause carries domain information with no filler.

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-parameter read-only search tool with 100% schema coverage and no output schema, the description supplies the domain context an agent needs (series meaning, file semantics). Only the lack of explicit usage routing to siblings leaves a minor 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 baseline is 3, but the description genuinely adds meaning to the required 'serie' enum by expanding 'anc' to economic inclusion and 'is' to social inclusion, which the schema only lists as opaque codes. This is real value beyond the structured field.

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 resource (infoMIES monthly program databases) and enumerates the two series, distinguishing content types. It is clearly a search/lookup tool, though it does not explicitly distinguish itself from the sibling search_infomies_boletines_zonales, so no sibling differentiation is present.

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 explains domain facts (the two series, that closed years have one year-end file, that .rar entries yield links only) but never states when to use this tool versus alternatives or any prerequisites. Usage is only implied through the content description.

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