Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Descargar y leer un informe del IG-EPN

get_informe_igepn
Read-only

Download and extract the full text of an IG-EPN seismic or volcanic report by exact name, year, group, and page range for analysis.

Instructions

Download and extract the text of one IG-EPN report from search_informes_igepn, re-located by exact nombre, grupo and anio (plus volcan when names repeat). pages limits the range (max 20/call).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
anioNoReport year (0 = current year) -- same value used to find it
grupoNo"sismico" | "volcanico" | "" (both) -- same value used to find it
pagesNoPage range, 1-indexed (e.g. "3", "1-5").
formatNotext summary (default) or json structured result.text
nombreYesExact report name from search_informes_igepn (e.g. "Informe Diario 2022-071")
volcanNoVolcano name, only needed to disambiguate a duplicate nombre

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.10.0
    • addedInput schema / properties / anio / description
      Added value: +"Report year (0 = current year) -- same value used to find it"
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / grupo / description
      Added value: +"\"sismico\" | \"volcanico\" | \"\" (both) -- same value used to find it"
    • addedInput schema / properties / nombre / description
      Added value: +"Exact report name from search_informes_igepn (e.g. \"Informe Diario 2022-071\")"
    • addedInput schema / properties / pages / description
      Added value: +"Page range, 1-indexed (e.g. \"3\", \"1-5\")."
    • addedInput schema / properties / volcan / description
      Added value: +"Volcano name, only needed to disambiguate a duplicate nombre"
  2. Changed8 schema fields changedv0.8.14
    • removedInput schema / properties / anio / title
      Removed value: -"Anio"
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / grupo / title
      Removed value: -"Grupo"
    • removedInput schema / properties / nombre / title
      Removed value: -"Nombre"
    • removedInput schema / properties / pages / title
      Removed value: -"Pages"
    • removedInput schema / properties / volcan / title
      Removed value: -"Volcan"
    • removedInput schema / title
      Removed value: -"get_informe_igepnArguments"
    • removedOutput schema / title
      Removed value: -"get_informe_igepnDictOutput"
  3. First observedv0.8.12

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/openWorld/destructive=false, so the safety profile is covered. The description adds real behavioral context beyond that: the page-range limit of 'max 20/call' and the disambiguation rule (volcan only when names repeat). It doesn't cover failure modes or pagination beyond pages, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence carries the workflow, disambiguation rule, and page cap with no filler. It is somewhat run-on (parenthetical nesting), which keeps it from a 5, but 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?

With an output schema present, return values needn't be explained, and the description adequately covers the search-then-fetch workflow, disambiguation, and the page cap for a 6-param tool. Minor gaps (behavior when the report is missing) are tolerable given the rich schema.

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 contributes a constraint absent from the schema: 'pages limits the range (max 20/call)'. It also ties nombre/grupo/anio/volcan semantics to the re-location workflow, adding meaning over raw field descriptions.

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 pair (download and extract text) and a precise resource (one IG-EPN report), and explicitly ties itself to the search_informes_igepn sibling as its source. An agent can distinguish this retrieval tool from the search tool without opening either 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?

Clearly frames the workflow: the report comes 'from search_informes_igepn' and must be re-located by the same nombre/grupo/anio values, with volcan only when names repeat. This tells the agent when to use it and how it relates to the search step, though it doesn't explicitly state what to do if the report isn't found.

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