EcuDataMCP

Overview Schema Source Related Servers Discussions Admin

Ver serie de un indicador diario del BCE

get_bce_indicador_diario

Read-only

Retrieve a BCE daily or monthly indicator by file and variable code, returning the most recent N observations or a date range (max 366 rows) for analysis.

Instructions

One BCE daily/monthly indicator (archivo and codigo from list_catalogo(fuente='bce_diarios')): the last ultimos_n points or a date range, capped at 366 rows.

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": {
      "archivo": "<archivo>",
      "codigo": "<codigo>"
    },
    "name": "get_bce_indicador_diario"
  }
}

Input Schema

Name	Required	Description	Default
`desde`	No	Optional start date YYYY-MM-DD.
`hasta`	No	Optional end date YYYY-MM-DD.
`codigo`	Yes	A "Código Variable Dinámica" from that same archivo.
`format`	No	text summary (default) or json structured result.	text
`archivo`	Yes	A file name from list_catalogo(fuente='bce_diarios').
`ultimos_n`	No	Most recent N observations when no date range is given.

Output Schema

Name	Required	Description	Default
`source`	No
`metadatos`	Yes
`url_fuente`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.15.0Nov 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "metadatos": {
+      "properties": {
+        "contrato": {
+          "const": "ecudatamcp.response.v1"
+        }
+      },
+      "required": [
+        "contrato"
+      ],
+      "type": "object"
+    },
+    "source": {},
+    "url_fuente": {}
+  },
+  "required": [
+    "metadatos"
+  ],
+  "type": "object"
+}

Changed1 schema field changedv0.13.0Oct 17, 2026

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null

Changed1 schema field changedv0.11.0Oct 3, 2026

changedInput schema / properties / archivo / description

Previous value: -"A file name from list_bce_indicadores_diarios."New value: +"A file name from list_catalogo(fuente='bce_diarios')."

Changed6 schema fields changedv0.10.0Sep 28, 2026

addedInput schema / properties / archivo / description

Added value: +"A file name from list_bce_indicadores_diarios."

addedInput schema / properties / codigo / description

Added value: +"A \"Código Variable Dinámica\" from that same archivo."

addedInput schema / properties / desde / description
```
Added value: +"Optional start date YYYY-MM-DD."
```

addedInput schema / properties / format / description

Added value: +"text summary (default) or json structured result."

addedInput schema / properties / hasta / description
```
Added value: +"Optional end date YYYY-MM-DD."
```

addedInput schema / properties / ultimos_n / description

Added value: +"Most recent N observations when no date range is given."

Changed8 schema fields changedv0.8.14Sep 27, 2026
- removedInput schema / properties / archivo / title
```
Removed value: -"Archivo"
```
- removedInput schema / properties / codigo / title
```
Removed value: -"Codigo"
```
- removedInput schema / properties / desde / title
```
Removed value: -"Desde"
```
- removedInput schema / properties / format / title
```
Removed value: -"Format"
```
- removedInput schema / properties / hasta / title
```
Removed value: -"Hasta"
```
- removedInput schema / properties / ultimos_n / title
```
Removed value: -"Ultimos N"
```
- removedInput schema / title
```
Removed value: -"get_bce_indicador_diarioArguments"
```
- removedOutput schema / title
```
Removed value: -"get_bce_indicador_diarioDictOutput"
```
First observedv0.8.12Sep 27, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The annotations already establish that this is a read-only, non-destructive, open-world operation. The description adds meaningful behavioral detail beyond that: results are capped at 366 rows and can be selected either by most recent N observations or by a date range.

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?

The definition is a single dense sentence with the key constraints front-loaded: what is returned, where the identifiers come from, and how the observation window works. There is no unnecessary wording.

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 full schema coverage, annotations, and an output schema, the description supplies the remaining operational context: source catalog, dual selection modes, and row cap. It is nearly complete, though it could mention sibling differentiation for an agent choosing between related BCE indicator tools.

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 the parameters are already well documented. The description reinforces the relationship between archivo, codigo, and list_catalogo, and clarifies the two selection modes, but adds limited new meaning 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?

The description clearly states that it returns one BCE daily/monthly indicator series, identified by archivo and codigo from list_catalogo(fuente='bce_diarios'). It is specific about the resource and required source identifiers, but it does not explicitly distinguish itself from the similarly named sibling get_indicador_bce.

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?

It gives useful call context: archivo and codigo must come from list_catalogo(fuente='bce_diarios'), and selection is either by ultimos_n or by date range. However, it does not say when to prefer this tool over related siblings such as get_indicador_bce, so alternative routing is left implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server