Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Horarios de cortes de luz por sector

get_cortes_horarios
Read-only

Parse Ecuador power-cut PDFs into structured outage rows: date, time blocks, location, sectors; filter results by place.

Instructions

Parse one power-cut PDF (archivo from search_cortes) into rows: date, time blocks without power, location (EEQ: substation; Centrosur: province/canton/zone) and sectors. query filters by place.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoFree text matched (accent-insensitive) against location and sectors, e.g. "La Floresta", "Gualaceo".
formatNotext summary (default) or json structured result.text
archivoYesThe file's `archivo` from search_cortes (EEQ: slug or URL; Centrosur: PDF URL).
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/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is carried structurally. The description adds the distribuidora-dependent output shape (EEQ substation vs Centrosur province/canton/zone), but says nothing about malformed-PDF handling, failure modes, or size/rate constraints.

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 sentences, zero filler, front-loaded with the verb and resource; the output fields and the query behavior are packed in without redundancy.

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 read-only parse tool with full schema coverage and no output schema, the description adequately covers the input provenance and the shape of the returned rows. It would be fully complete with a note on how unresolvable or unparseable PDFs are reported.

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 all four parameters are already documented, including the accent-insensitive `query` matching and both enums. The description only restates that query filters by place and confirms the archivo provenance, adding little beyond the schema.

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 a specific verb and resource ("Parse one power-cut PDF") plus the exact fields it yields (date, time blocks, location, sectors), so it is immediately distinguishable from search_cortes, which only locates files.

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 names the prerequisite sibling and the input it supplies ("archivo from search_cortes"), which establishes the find-then-parse workflow. It does not state explicit exclusions or when not to call it, so it stops short of a full when/when-not routing rule.

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