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 Ecuador's live grid snapshots of generation mix and demand for real-time, daily, monthly, or annual periods. Use for current dashboard data, not 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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  2. 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"
  3. First observedv0.8.12

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds that the data is a live/real-time snapshot and excludes historical queries, but says nothing about freshness, update cadence, or error conditions.

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?

Two tight sentences, front-loaded with the resource and scope followed by the exclusion. Nothing is wasted, though it is terse enough to leave gaps.

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 an output schema present and safety annotations covering the operation, the description supplies the essential scope plus the historical-query exclusion. It is complete enough to call correctly, missing only minor behavioral detail.

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% with both enums documented, so the schema already carries the parameter burden. The description's 'now, yesterday, month or year to date' loosely maps to the tablero enum values, adding marginal orientation but no syntax or selection guidance.

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 and scope: 'CENACE live grid snapshot: generation mix and demand' with temporal ranges. The 'No historical queries' clause helps separate it from historical-data siblings, though it does not name a specific alternative.

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 phrase 'No historical queries' is an implicit when-not and the time ranges ('now, yesterday, month or year to date') imply when to use it. However, no sibling tool is named and no explicit alternative for historical data is offered.

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