iran-quake-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IRAN_QUAKE_MCP_PROXY | No | Optional HTTP proxy URL (comma list allowed); system proxy settings are ignored. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| eq_latestA | List the most recent earthquakes in Iran, newest first. Use for "was there an earthquake today?". Times: time_utc and time_tehran (UTC+03:30); depth_km in km; magnitude type in mag_type (mb, ml, mw...). Call eq_detail with an id for more, eq_stats for counts. |
| eq_searchA | Search earthquakes in Iran by date range, magnitude, bounding box and place text. Use for history ("M5+ in 2026", "quakes near Bam"). USGS and EMSC have no province field: USGS gives the nearest
town ('70 km NNE of Minab, Iran'), EMSC a region ('SOUTHERN IRAN'); filter by |
| eq_significantA | List the strongest recent earthquakes in Iran, largest magnitude first. Use for "biggest earthquakes this month/year". Times in UTC and Tehran (UTC+03:30), depth_km in km. |
| eq_detailA | Get one earthquake in full: location, depth_km, magnitude type and source quality fields. The source is detected from the id format (IRSC: plain number, found only in its latest ~20 events, adds the nearest towns). USGS adds review status, shaking (felt reports, cdi, mmi), tsunami flag, sig (significance 0-1000), nst (stations), gap (degrees), rms; EMSC adds the contributing agency (catalog) and last update. Times in UTC and Tehran (UTC+03:30). |
| eq_statsA | Count earthquakes in Iran over a window: by magnitude band, by place, plus the strongest event. Use for "how active has Iran been this month". Places are USGS nearest towns or EMSC regions (no province
data). |
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 5 tools
Each tool has a recognizable role: free-form filtered search, newest-first list, strongest-first list, single-event detail, and aggregate counts. However, eq_search, eq_latest, and eq_significant all return event lists and differ mainly in sort/filter semantics, so a sloppy agent could pick the wrong one; the descriptions do a good job clarifying when to use each.
All names use the eq_ prefix with snake_case, which is highly predictable and readable. The one deviation is that search/detail are verb-like while latest/significant/stats are nouns/adjectives, so the verb_noun pattern isn't strictly uniform.
Five tools is well-scoped for an Iran earthquake service: discovery (search/latest/significant), retrieval (detail), and aggregation (stats). No tool feels redundant or padded.
The surface covers the core lifecycle: find events by time/place/magnitude, get newest and largest, fetch full detail, and compute activity counts. Gaps are minor (no source/catalog listing or station/network metadata), but nothing blocks typical agent workflows.