Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar informes sísmicos y volcánicos del IG-EPN

search_informes_igepn
Read-only

Search IG-EPN PDF reports by year, group, or keyword to find seismic bulletins and volcanic alerts; then read selected reports. For raw earthquake data, use search_sismos.

Instructions

Search IG-EPN's PDF report archive: seismic bulletins and volcanic alerts/reports, by year and group. Next: get_informe_igepn to read one. For raw earthquake data use search_sismos.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
anioNoReport year (0 = current year)
grupoNo"sismico" | "volcanico" | "" (both)
limitNoMax reports to return (default 15, max 30)
queryNoFree text over report name/volcano (e.g. "cotopaxi", "trimestral")
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. Changed5 schema fields changedv0.10.0
    • addedInput schema / properties / anio / description
      Added value: +"Report year (0 = current year)"
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / grupo / description
      Added value: +"\"sismico\" | \"volcanico\" | \"\" (both)"
    • addedInput schema / properties / limit / description
      Added value: +"Max reports to return (default 15, max 30)"
    • addedInput schema / properties / query / description
      Added value: +"Free text over report name/volcano (e.g. \"cotopaxi\", \"trimestral\")"
  3. Changed7 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 / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"search_informes_igepnArguments"
    • removedOutput schema / title
      Removed value: -"search_informes_igepnDictOutput"
  4. First observedv0.8.12

TDQS

A4.2/5.0
Behavior3/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 structurally. The description adds that the corpus is PDF reports and hints at a two-step retrieve-then-read workflow, but says nothing about result volume, pagination, or ranking behavior. Adequate but not rich given the annotations do the heavy lifting.

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 that are entirely front-loaded: the verb+resource+scope comes first, then the next-step and alternative routing. No sentence is filler; each 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?

Five optional parameters, no required params, no output schema, and annotations covering safety - so the description only needs to establish scope and routing, which it does. The minor gap is that it does not describe what a result record looks like or how 'limit' interacts with the archive size, but that is largely handled by the schema.

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 five parameters (anio, grupo, limit, query, format) are already documented in the schema, including the '0 = current year' and '"" = both' conventions. The description adds no parameter syntax or semantics beyond what the schema provides, 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 a specific verb (Search) and resource (IG-EPN's PDF report archive: seismic bulletins and volcanic alerts/reports) plus the scoping dimension (by year and group). It is clearly distinguishable from siblings search_sismos (raw earthquake data) and get_informe_igepn (reading a single report).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: 'Next: get_informe_igepn to read one' establishes the follow-up step, and 'For raw earthquake data use search_sismos' names the alternative and the condition that selects it. Both when-to-use-this and when-to-use-something-else are covered.

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