igepn-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IGEPN_DB | No | SQLite path (WAL; poller and server can share it). | data/igepn.db |
| IGEPN_CHANNEL | No | Telegram channel. | SismosVolcanesIGEPN |
| IGEPN_MCP_TOKEN | No | Bearer token required on HTTP (/healthz stays open). | |
| IGEPN_USER_AGENT | No | User agent for requests; set to identify your deployment. | honest UA |
| IGEPN_POLL_MINUTES | No | >0: serve also polls in the background (no timer needed); 3 recommended. | 0 |
| IGEPN_FETCH_TIMEOUT | No | Fetch timeout in seconds. | 20 |
| IGEPN_MAX_CATCHUP_PAGES | No | Pages one poll may walk back to reach the watermark after downtime. | 25 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| last_quakeA | The single most recent earthquake reported by the IGEPN, with its latest (revised if available) values. Use for "¿qué fue ese temblor?", "what was that earthquake just now", "did it just shake?". |
| latest_quakesA | 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". |
| volcano_statusA | Latest IGEPN activity report for Ecuadorian volcanoes: surface and internal activity level, each with its trend. Use for "how is the Sangay", "is Cotopaxi active", "volcano status". |
| ig_alertsA | Recent IGEPN instant bulletins (#IGAlInstante: lahars, ash emissions, increased activity) and special volcano reports, newest first, as IGEPN wrote them. Use for "any volcano alerts", "is there ash from the Sangay", "lahar warnings". Relay safety recommendations exactly as written. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: last_quake fetches a single most-recent event, latest_quakes lists events with filters, volcano_status provides activity reports, and ig_alerts delivers bulletins. The descriptions explicitly differentiate use cases, leaving no ambiguity.
All names use snake_case consistently, but the structural patterns vary (adjective_noun, noun_noun, abbreviation_noun). This minor deviation from a uniform pattern prevents a perfect score.
Four tools are well-scoped for a focused monitoring server, covering core needs of recent earthquakes, volcano status, and alerts without redundancy. Each tool earns its place.
The surface covers the main earthquake and volcano information needs, but lacks detailed historical querying beyond hourly windows or event-specific lookups. These minor gaps are workable with existing filters.