Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Recuperar snapshot del portal nacional de cortes (energia-ecuador.com, 2024)

get_energia_ecuador_snapshot
Read-only

Retrieve an archived 2024-04-24 Wayback snapshot of Ecuador's defunct blackout-schedule portal, covering only EEQ's Pichincha rotation; search by canton or sector. Use for historical lookups only.

Instructions

Frozen Wayback Machine copy (2024-04-24) of the defunct national blackout-schedule portal energia-ecuador.com; only EEQ's Pichincha rotation survived. For current schedules use search_cortes and get_cortes_horarios.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoFree text matched (accent-insensitive) against canton or sectores.
formatNotext summary (default) or json structured result.text

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 / query / description
      Added value: +"Free text matched (accent-insensitive) against canton or sectores."
  3. Changed4 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"get_energia_ecuador_snapshotArguments"
    • removedOutput schema / title
      Removed value: -"get_energia_ecuador_snapshotDictOutput"
  4. First observedv0.8.12

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, openWorld), so the description doesn't need to. What it adds beyond them is substantive data-quality context: the source portal is defunct, the data is frozen at a specific date, and coverage is partial (only one rotation survived). That staleness/completeness warning is exactly what an agent needs to avoid treating this as live data.

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 clauses: the identifying fact (what the snapshot is and its limits) is front-loaded, followed immediately by the redirect to live alternatives. No filler, every clause carries decision-relevant 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?

For a two-parameter, optional-parameter read-only snapshot tool with no output schema, the description supplies the essentials: source, date, coverage limitation, and alternatives. It doesn't describe the shape of the returned rotation data, which would help an agent interpret results, but the gap is minor given the tool's simplicity.

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 both `query` (accent-insensitive match against canton or sectores) and `format` (text|json, with default) are fully documented in the schema. The description adds no extra syntax, scope, or default guidance, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States precisely what the tool returns: a frozen Wayback Machine copy (dated 2024-04-24) of a specific defunct portal, including its coverage limitation (only EEQ's Pichincha rotation survived). It names the sibling tools it must not be confused with (search_cortes, get_cortes_horarios), so an agent can disambiguate without opening any schema.

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?

Explicitly routes the agent to search_cortes and get_cortes_horarios for current schedules, which implicitly confines this tool to historical/snapshot queries. It stops short of stating the positive trigger (e.g., 'use this when you need pre-2024 EEQ Pichincha data'), leaving a small inference gap.

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