Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar sismos recientes en Ecuador

search_sismos
Read-only

Search Ecuador's IG-EPN catalog for recent earthquakes by location, minimum magnitude, and days; returns magnitude, depth, coordinates, time, and place.

Instructions

Recent earthquakes from the IG-EPN catalog feed: magnitude, depth, coordinates, time and place. Filter by text, minimum magnitude and days.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
diasNoOnly events from the last N days (0 = all available)
limitNoMax events to return (default 15, max 100)
queryNoFree text over location/id (e.g. "Quito", "Esmeraldas")
formatNotext summary (default) or json structured result.text
magnitud_minimaNoMinimum magnitude (e.g. 4.0)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.10.0
    • addedInput schema / properties / dias / description
      Added value: +"Only events from the last N days (0 = all available)"
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / limit / description
      Added value: +"Max events to return (default 15, max 100)"
    • addedInput schema / properties / magnitud_minima / description
      Added value: +"Minimum magnitude (e.g. 4.0)"
    • addedInput schema / properties / query / description
      Added value: +"Free text over location/id (e.g. \"Quito\", \"Esmeraldas\")"
  2. Changed7 schema fields changedv0.8.14
    • removedInput schema / properties / dias / title
      Removed value: -"Dias"
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / magnitud_minima / title
      Removed value: -"Magnitud Minima"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"search_sismosArguments"
    • removedOutput schema / title
      Removed value: -"search_sismosDictOutput"
  3. First observedv0.8.12

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds provenance (IG-EPN catalog feed) and the returned dimensions, but says nothing about freshness/latency, rate limits, or result ordering beyond what the annotations and output schema imply.

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?

Two tight sentences with no waste, front-loading the resource and data source before the filtering capabilities. Appropriately sized for a simple search tool.

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 covering return values and annotations covering the safety profile, the description only needs to establish purpose and filtering, which it does. Minor gap is the absence of any sibling disambiguation for a catalog with many search_* tools.

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 the schema already documents all five parameters including defaults, enum and examples. The description's filter summary (text, magnitude, days) adds no syntax or format detail beyond what the schema provides; baseline 3 applies.

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?

States a specific verb (search) and resource (recent earthquakes/sismos) plus the data source (IG-EPN catalog feed) and the fields returned. It is clearly distinct from siblings like search_informes_igepn or search_eventos_riesgo, though it does not explicitly name the nearest alternative.

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

Usage Guidelines3/5

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

"Filter by text, minimum magnitude and days" implies how to narrow results, giving usable context for invocation. However, there is no explicit when-to-use/when-not guidance and no mention of how this differs from related seismic siblings such as search_eventos_riesgo or search_informes_igepn.

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