Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar cronogramas de cortes de luz

search_cortes
Read-only

Search scheduled power-cut PDFs for Ecuador's eeq or centrosur utilities by date, period, or title; retrieve file references to analyze outage schedules.

Instructions

Scheduled power-cut PDFs of one utility: eeq (Quito, 2023-2024 blackout crises) or centrosur (Azuay, Cañar, Morona Santiago, 2023 on). Next: get_cortes_horarios with a file's archivo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoFree text matched (accent-insensitive) against the file's period, date, title or URL, e.g. "noviembre", "2024-10".
formatNotext summary (default) or json structured result.text
distribuidoraYeseeq or centrosur.

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. Addedv0.10.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuinely new behavior: results are PDF file listings and the required continuation is passing a file's 'archivo' to get_cortes_horarios. Pagination and rate limits are unstated, keeping it from a 5.

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 tight sentences with zero filler: the resource scope is front-loaded and the follow-up step is appended last. Every clause earns its place.

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?

There is no output schema, but the description conveys the return type (PDFs) and the next action, which is what an agent needs for this search tool. Missing detail on result format or counts keeps it just short of complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning by expanding the bare enum values 'eeq'/'centrosur' with their geography and date ranges (Quito 2023-2024; Azuay, Cañar, Morona Santiago 2023 on), which helps an agent choose the right distribuidora.

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 concrete resource (scheduled power-cut PDFs) and scopes it to two specific utilities with geography and time coverage, so an agent knows exactly what corpus is searched. The verb is only implied by the tool name rather than stated outright, which keeps it short of a 5.

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?

It explicitly routes the agent forward: 'Next: get_cortes_horarios with a file's archivo.' That is a clear workflow instruction naming the sibling. It does not state when not to use this tool, but there is no competing cortes-search sibling, so the gap is minor.

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