Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Consultar reporte estadístico de ARCONEL

get_arconel_reporte
Read-only

Fetch rows from an ARCONEL report by type and year, with optional month and group filters. Pagination limits results and indicates if all pages were read.

Instructions

Run one ARCONEL report (e.g. "Balance Energía" for a year) and return its rows. Slow, ~50 rows per page; max_paginas caps work and completo says if everything was read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mesNo1-12, only for report types with a month filter (e.g. per-parish reports); others already break down by month.
anioYesYear, 1998-current.
tipoYesReport name as listed by `list_catalogo(fuente='arconel')` (accent/case-insensitive), e.g. "Balance Energía", "Pérdidas", "Medidores Catastro".
grupoNotodos | cnel | empresas_electricas.todos
formatNotext summary (default) or json structured result.text
max_paginasNoMaximum pages to read (1-40, default 10).

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. Changed1 schema field changedv0.11.0
    • changedInput schema / properties / tipo / description
      Previous value: -"Report name as listed by `list_arconel_reportes` (accent/case-insensitive), e.g. \"Balance Energía\", \"Pérdidas\", \"Medidores Catastro\"."New value: +"Report name as listed by `list_catalogo(fuente='arconel')` (accent/case-insensitive), e.g. \"Balance Energía\", \"Pérdidas\", \"Medidores Catastro\"."
  3. Changed6 schema fields changedv0.10.0
    • addedInput schema / properties / anio / description
      Added value: +"Year, 1998-current."
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / grupo / description
      Added value: +"todos | cnel | empresas_electricas."
    • addedInput schema / properties / max_paginas / description
      Added value: +"Maximum pages to read (1-40, default 10)."
    • addedInput schema / properties / mes / description
      Added value: +"1-12, only for report types with a month filter (e.g. per-parish reports); others already break down by month."
    • addedInput schema / properties / tipo / description
      Added value: +"Report name as listed by `list_arconel_reportes` (accent/case-insensitive), e.g. \"Balance Energía\", \"Pérdidas\", \"Medidores Catastro\"."
  4. Changed8 schema fields changedv0.8.14
    • removedInput schema / properties / anio / title
      Removed value: -"Anio"
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / grupo / title
      Removed value: -"Grupo"
    • removedInput schema / properties / max_paginas / title
      Removed value: -"Max Paginas"
    • removedInput schema / properties / mes / title
      Removed value: -"Mes"
    • removedInput schema / properties / tipo / title
      Removed value: -"Tipo"
    • removedInput schema / title
      Removed value: -"get_arconel_reporteArguments"
    • removedOutput schema / title
      Removed value: -"get_arconel_reporteDictOutput"
  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 declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so safety is covered. The description adds real behavioral value: calls are slow, ~50 rows per page, max_paginas caps the work, and the 'completo' flag reveals truncation. That is genuinely useful operational context beyond 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.

Conciseness5/5

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

Two compact sentences with zero filler. The purpose and example lead, then the performance/truncation reality is front-loaded so the agent plans paging before calling.

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 paged, slow statistical-report tool with no output schema, the description supplies the operational facts an agent needs: slowness, rows per page, page cap, and completeness flag. It stops short of describing row shape, but the format parameter and json option make the return sufficiently predictable.

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 coverage is 100%, so all six parameters are documented including the mes month-filter caveat and the tipo catalog lookup. The description's mention of max_paginas and completo only restates schema semantics. Baseline 3 is appropriate; little added 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?

States a specific verb (run) and resource (one ARCONEL report) with an example report name, so the agent can tell it apart from list_catalogo or generic search siblings. It doesn't explicitly name siblings but the ARCONEL domain and report-row return make its scope clear.

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 example 'Balance Energía' for a year implies the expected call, and the tipo description points to list_catalogo(fuente='arconel') for discovery. But the description itself gives no explicit when-to-use or when-not-to-use guidance relative to list_catalogo or the other statistical 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