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 text of an IG-EPN report by exact name, year, and group; disambiguate duplicates with volcano and limit pages per call.

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

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

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real operational context beyond them: a per-call page cap (max 20) and the fact that identification keys must match the search call. It says nothing about auth or error behavior, keeping it at 4.

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 dense sentences with the identification mechanism front-loaded and the page constraint trailing. No filler, no restatement of the title, every clause carries 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 no-output-schema retrieval tool, the description covers identification, pagination limits and the format toggle that governs the return shape. It does not describe what a caller gets when a nombre matches nothing or how large extractions are chunked beyond the page cap, leaving a small gap.

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 and the schema already documents all six parameters. The description adds the 'max 20 pages/call' constraint, which the schema's pages field does not state, and frames nombre/grupo/anio as reused search keys. That extra constraint earns one step above baseline.

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) plus a precisely scoped resource (one IG-EPN report), and names the sibling it depends on (search_informes_igepn). An agent can distinguish it from the search sibling 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?

The description establishes a clear discovery-then-retrieval workflow: the report comes 'from search_informes_igepn' and is re-located by the exact values used there, with volcan needed only when names repeat. It lacks an explicit exclusion or 'do not use for X' clause, so it stops short of a full 5.

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