Skip to main content
Glama
Sign In
EcuDataMCP

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar bases mensuales de infoMIES

search_infomies_bases_mensuales
Read-only

Search infoMIES monthly program databases for economic inclusion (anc) or social inclusion (is) by year or keyword; closed years include year-end files and .rar links.

Instructions

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "serie": "<serie>"
    },
    "name": "search_infomies_bases_mensuales"
  }
}

Input 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

NameRequiredDescriptionDefault
totalNo
offsetNo
sourceNo
metadatosYes
url_fuenteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.15.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "metadatos": {
+      "properties": {
+        "contrato": {
+          "const": "ecudatamcp.response.v1"
+        }
+      },
+      "required": [
+        "contrato"
+      ],
+      "type": "object"
+    },
+    "offset": {},
+    "source": {},
+    "total": {},
+    "url_fuente": {}
+  },
+  "required": [
+    "metadatos"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changedv0.13.0
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  3. 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\"."
  4. 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"
  5. First observedv0.8.12

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, open-world, non-destructive behavior, and the description adds two facts those annotations cannot convey: closed years contain a single year-end file, and .rar artifacts are returned as links only (no extracted contents). Those are exactly the operational caveats an agent needs before calling, though nothing is said about result size or how monthly files are shaped for open years.

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 sentences with no filler, and the resource plus series definitions are front-loaded ahead of the caveats. Slightly telegraphic phrasing ('links only') costs a little clarity 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 a full input schema and an output schema present, return-format explanation is unnecessary, and the description covers the domain-specific things the schema cannot: series semantics, closed-year file consolidation, and the link-only nature of .rar results. Only the adjacent-tool boundary is left unaddressed.

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 would be 3, but the description earns an increment by defining the required enum values ('anc' = economic inclusion, 'is' = social inclusion), which the schema only restates as bare strings. The 'closed years → one year-end file' note also adds meaning to the anio parameter.

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?

The description opens with a specific resource ('infoMIES monthly program databases') and immediately names the two series, so the agent knows exactly which collection is being searched. It does not distinguish this tool from its closest sibling (search_infomies_boletines_zonales) or any other infoMIES tool, which keeps it out of the 5 band.

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?

Usage is implied rather than stated: the agent can infer it should call this when it needs monthly program databases and must pick 'anc' or 'is'. 'Closed years have one year-end file' gives useful availability context, but there is no explicit when-to-use/when-not-to-use guidance or referral to an alternative tool.

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