Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Ver un tablero en vivo de CENACE

get_cenace_tablero
Read-only

Fetch CENACE live grid snapshots for Ecuador: current generation mix and demand, yesterday, month-to-date or year-to-date. Use for real-time and cumulative dashboards; no historical queries.

Instructions

CENACE live grid snapshot: generation mix and demand now, yesterday, month or year to date. No historical queries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNotext summary (default) or json structured result.text
tableroYesOne of the 5 names above.

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. Changed2 schema fields changedv0.10.0
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / tablero / description
      Added value: +"One of the 5 names above."
  3. Changed4 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / tablero / title
      Removed value: -"Tablero"
    • removedInput schema / title
      Removed value: -"get_cenace_tableroArguments"
    • removedOutput schema / title
      Removed value: -"get_cenace_tableroDictOutput"
  4. First observedv0.8.12

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld and non-destructive, so the safety profile is covered. The description adds genuine value beyond that: the snapshot is point-in-time and limited to now/yesterday/month/year-to-date, with no historical depth.

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 tightly packed sentences with the resource and scope front-loaded and the limiting condition placed at the end. No filler, every clause carries information.

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 no output schema, the description does indicate what comes back (generation mix and demand figures). A snapshot tool of this complexity is adequately covered, though it could say a bit more about the returned shape.

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% with both enums documented, so the schema does the heavy lifting. The phrase "now, yesterday, month or year to date" loosely echoes the five tablero values but does not map them explicitly, so no credit above the baseline.

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 resource (CENACE live grid) and content (generation mix and demand), with the time granularities spelled out. It is clearly distinguishable from unrelated siblings, though it does not explicitly differentiate itself from the nearby get_energia_ecuador_snapshot.

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

Usage Guidelines4/5

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

"No historical queries" is an explicit when-not condition that bounds the tool's use. It does not, however, name an alternative tool for historical energy data, leaving the agent to search siblings on its own.

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