Skip to main content
Glama

Better Llama — Chile data

Sismos en Chile (USGS)

get_chile_earthquakes
Read-onlyIdempotent

Lista sismos ocurridos en Chile (o en un radio desde una coordenada) con magnitud, profundidad, lugar, hora en UTC y en Chile, alerta PAGER y bandera de tsunami del USGS, filtrando por fechas y magnitud. Datos de dominio público del USGS. No es un sistema de alerta temprana: para emergencias consulta SENAPRED/SHOA. / Earthquakes in Chile from USGS.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_chile_earthquakes"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoZona — Caja geográfica de búsqueda.chile
toDateNoHasta (AAAA-MM-DD, hora de Chile) — Vacío = hoy.
orderByNoOrden — Orden de los resultados.time
feltOnlyNoSolo sismos percibidos (reportes 'Did You Feel It?') — Eventos con al menos un reporte de percepción.
fromDateNoDesde (AAAA-MM-DD, hora de Chile) — Vacío = 7 días antes de 'Hasta'. Rango máximo 10 años.
latitudeNoLatitud (radio) — Ej. -33.45 (Santiago).
maxItemsNoMáximo de resultados a devolver (1-500). Por defecto 20.
radiusKmNoRadio (km) — Por defecto 100 km.
longitudeNoLongitud (radio) — Ej. -70.66.
onlyChileNoSolo sismos ubicados en Chile — Descarta eventos cuyo lugar USGS es Argentina, Bolivia o Perú. Por defecto activado salvo en 'radio'.
maxDepthKmNoProfundidad máxima (km) — Opcional.
tsunamiOnlyNoSolo con bandera de tsunami — Bandera informativa del USGS; NO es una alerta oficial del SHOA/SENAPRED.
maxMagnitudeNoMagnitud máxima — Opcional.
minMagnitudeNoMagnitud mínima — Por defecto 2.5.
minAlertLevelNoAlerta PAGER mínima — Solo eventos con alerta de impacto PAGER del USGS igual o superior.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds real context beyond that: USGS provenance, public-domain data, the informative-only nature of the tsunami flag, and the PAGER alert semantics. It does not discuss response size limits, pagination or failure modes, which keeps it below 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?

Core capability is front-loaded in the first clause, followed by the returned fields and then the safety caveat. The trailing English one-liner partially duplicates what the preceding Spanish sentence already said, which is the only real slack in an otherwise tight definition.

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 15 optional parameters and no output schema, the description carries the burden of describing the return shape, and it does so by listing the fields each event yields. Combined with the disclaimers about tsunami flags and emergency response, an agent has what it needs; only pagination/volume behavior is left unaddressed.

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 coverage is 100%, so every one of the 15 parameters is already documented in the schema, including defaults and ranges (10-year max span, 1-500 items). The description only restates that filtering is by date and magnitude, adding no syntax or edge-case meaning beyond the schema; baseline 3 is appropriate.

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 precise verb and resource (list earthquakes in Chile, or within a radius of a coordinate) and enumerates the returned fields: magnitude, depth, place, UTC/Chile time, PAGER alert, tsunami flag. The scope and filters are clear enough that an agent can distinguish it from every listed sibling, none of which touch seismic data.

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 description bounds the domain by naming the filtering dimensions (dates, magnitude) and adds a clear 'when not to use' caveat: it is not an early-warning system, and emergencies belong to SENAPRED/SHOA. It offers no guidance on choosing between region modes or on when a radius search is preferable to the default Chile box beyond what the enum names imply.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources