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 infoMIES monthly databases for economic (anc) or social (is) inclusion programs, filtering by year or keyword.

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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\"."
  2. 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"
  3. First observedv0.8.12

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly=true, openWorld=true, destructive=false. Going beyond them, the description discloses return-shape behavior: closed years contain a single year-end file, and .rar entries are delivered as links only. That is useful context an agent cannot get from the annotations.

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?

Three short clauses, front-loaded with the resource and free of filler. It is telegraphic to the point that sentence fragments slightly reduce readability, but nothing is wasted.

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 an output schema present, return values need not be explained, and the annotations cover the safety profile. The description still contributes the series meanings and file-count/link behavior, leaving only cross-tool routing as a 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. The description adds meaning the schema lacks by expanding the serie enum (anc = economic inclusion, is = social inclusion), which is genuine semantic value beyond the bare '"anc" or "is"' in 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?

Names the specific resource (infoMIES monthly program databases) and distinguishes the two series with parenthetical expansions, so an agent knows it selects from 'anc'/'is' rather than the zonal-boletines sibling. The action verb (search/fetch) is only implied by the tool name, not stated in the description, so it falls short of a full 5.

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

Usage Guidelines2/5

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

There is no explicit when-to-use, when-not-to-use, or named alternative. The closest thing to guidance is the series gloss and the note about closed years, which help interpret results but do not tell an agent when to pick this tool over the numerous sibling search_* tools.

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