Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar sismos recientes en Ecuador

search_sismos
Read-only

Retrieve recent earthquakes from Ecuador's IG-EPN catalog, filter by location, minimum magnitude, and days, and view 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)

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 / 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\")"
  3. 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"
  4. 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=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the data source (IG-EPN catalog) and the returned field set, but says nothing about freshness, pagination, or how 'recent' is bounded beyond what the schema's dias parameter already states.

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, front-loaded with what the tool returns before the filter list. No filler, though the title's 'Buscar' is what supplies the action verb.

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 5 optional parameters but no output schema, the description usefully enumerates the returned fields and names the source, and the schema covers all filters. Enough for an agent to call it correctly; only the definition of 'recent' and any result-shape nuances are left implicit.

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 every parameter is already documented in the schema. The description's 'filter by text, minimum magnitude and days' merely restates query, magnitud_minima and dias without adding syntax, format, or edge-case detail. Baseline 3 applies when the schema does the heavy lifting.

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 resource (recent earthquakes) and its source (the IG-EPN catalog feed), plus the data fields surfaced (magnitude, depth, coordinates, time, place). The verb is carried by the title rather than the description, and no sibling is named to differentiate it from search_informes_igepn or search_eventos_riesgo, but the purpose is unmistakable.

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?

The second sentence explains what can be filtered (text, minimum magnitude, days), which implies usage, but there is no explicit when-to-use, when-not, or named alternative among the many search_* siblings. Guidance is inferable rather than stated.

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