Skip to main content
Glama
Sign In
EcuDataMCP

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Leer el boletín mensual de transacciones de CENACE

get_cenace_boletin
Read-only

Retrieve CENACE monthly electricity-market bulletins by year or month to access production, demand, prices, and Colombia/Peru trade data from 2019 onward.

Instructions

CENACE monthly electricity-market bulletin (2019 onward): production by resource, demand by distributor, average prices, trade with Colombia and Peru. Empty mes lists the issues; mes=YYYY-MM returns its text by page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_cenace_boletin"
  }
}

Input Schema

NameRequiredDescriptionDefault
mesNoEmpty to list the issues; YYYY-MM (e.g. 2026-07) or "ultimo" for one issue's text.
anioNoWith an empty mes, list only that year's issues.
formatNotext summary (default) or json structured result.text

Output Schema

NameRequiredDescriptionDefault
filasNo
sourceNo
columnasNo
metadatosYes
url_fuenteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.15.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real context beyond that: the 2019-onward coverage window, the two distinct behavior modes keyed on mes, and the fact that text is returned page by page. It does not explain pagination mechanics or how to advance pages, which is the main residual gap.

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?

Two sentences, zero waste. The subject and coverage window are front-loaded, followed by the content enumeration and then the mode rules, which is the right order for an agent scanning for fit.

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?

An output schema exists, so return-value explanation is not required, and the description covers content scope, date coverage, and the two retrieval modes. The remaining ambiguity — how multi-page text is delivered, and what happens for months with no issue — keeps this from a 5 for a tool with an open-world data source.

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 all three parameters (mes, anio, format) are already documented in the schema, including the 'ultimo' sentinel and the enum for format. The description restates the empty-mes vs YYYY-MM behavior and adds only a hint about paged text output, which is close to repeating structured data. Baseline 3 is appropriate.

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 names a specific resource (the CENACE monthly electricity-market bulletin) and enumerates its contents — production by resource, demand by distributor, average prices, trade with Colombia and Peru — plus a coverage window (2019 onward). An agent can tell this is a bulletin-reading tool rather than a dashboard or statistics tool. It stops short of explicitly contrasting itself with the sibling get_cenace_tablero, so it stays at 4 rather than 5.

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 guidance is present but limited to operating modes: empty mes lists the available issues, mes=YYYY-MM retrieves one issue's text. That tells the agent how to drive the tool but not when to prefer it over the sibling dashboard/tablero tool or what to do if a requested month is missing. Selection guidance is implied rather than stated.

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