Skip to main content
Glama
danmarce

igepn-mcp

by danmarce
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

latest_quakes

Read-only

Get recent earthquakes reported by IGEPN in Ecuador, filtered by time window, magnitude, and place. Check tremors near a city or strong quakes this month.

Instructions

Recent earthquakes reported by the IGEPN, newest first, one entry per event (its latest report). Use for "earthquakes today / this week", "any tremors near Quito?", "strong quakes this month".

    Args:
        hours: look-back window in hours (default 24; e.g. 168 = one week, 720 = 30 days).
        min_mag: only events with magnitude >= this (e.g. 4).
        place: text that must appear in the location, case/accent-insensitive: a city or province as IGEPN
            writes it, e.g. "Quito", "Manabí", "Esmeraldas" (IGEPN names the NEAREST town, so a quake felt
            in a city may be listed under a neighbouring one).
        n: max events (default 15, max 50).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nNo
hoursNo
placeNo
min_magNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely non-obvious behavior: the source is IGEPN, results are newest-first, repeated reports are collapsed to the latest entry per event, and IGEPN labels the NEAREST town — so a place match may miss the city where the quake was felt. That caveat is the kind of operational insight annotations cannot convey.

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?

Front-loaded summary sentence followed by a clean Args block; the usage examples earn their place by tying user phrasings to arguments. It is a little longer than strictly necessary, but there is no filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description still conveys the result shape (one entry per event, latest report, newest first) and documents all four optional parameters including bounds and defaults. Nothing needed to call the tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does so: hours with a default plus 168/720 conversions, min_mag as a >= threshold with an example, place with case/accent-insensitivity, examples and the nearest-town caveat, and n with default 15 and a max of 50. Every parameter gains meaning absent from the schema.

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?

The description states a specific verb+resource (recent earthquakes from IGEPN), the ordering (newest first), and the de-duplication semantics (one entry per event, latest report). That scope plus ordering implicitly separates it from the singular sibling last_quake, so an agent can route without opening the 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?

It gives concrete trigger phrases ('earthquakes today / this week', 'any tremors near Quito?', 'strong quakes this month') that map onto the hours/min_mag/place arguments, which is clear guidance about when to reach for this tool. It stops short of naming alternatives or stating exclusions relative to last_quake / ig_alerts, so it is not 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