Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
IGEPN_DBNoSQLite path (WAL; poller and server can share it).data/igepn.db
IGEPN_CHANNELNoTelegram channel.SismosVolcanesIGEPN
IGEPN_MCP_TOKENNoBearer token required on HTTP (/healthz stays open).
IGEPN_USER_AGENTNoUser agent for requests; set to identify your deployment.honest UA
IGEPN_POLL_MINUTESNo>0: serve also polls in the background (no timer needed); 3 recommended.0
IGEPN_FETCH_TIMEOUTNoFetch timeout in seconds.20
IGEPN_MAX_CATCHUP_PAGESNoPages 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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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?".

    Check `ago`: if the last quake is hours or days old, the tremor the user felt may not be reported yet
    (a PRELIMINAR report usually appears within ~5 minutes) - say so rather than guessing.
    When the event was revised, `preliminary` shows the first estimate for comparison.
    
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".

    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).
    
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".

    Without `volcano`: every volcano with a report in the last 30 days (IGEPN only publishes periodic
    reports for volcanoes it is actively following; others are not listed). With `volcano`: that
    volcano's latest report however old (check `report_date`) plus its recent instant alerts.

    Args:
        volcano: name, case/accent/space-insensitive, e.g. "Sangay", "reventador", "Cotopaxi".
    
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.

    Args:
        hours: look-back window in hours (default 48; 168 = one week).
        volcano: optional volcano name filter, e.g. "Sangay".
        n: max bulletins (default 10, max 50).
    

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 4 tools

Disambiguation5/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo issues