Skip to main content
Glama
Sign In
iran-quake-mcp

iran-quake-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Earthquake statistics

eq_stats
Read-onlyIdempotent

Count earthquakes in Iran over a time window by magnitude band and place, and find the strongest event. Use it to gauge recent seismic activity.

Instructions

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". truncated = the source returned its full 3000 rows before the Iran filter, so counts cover only the newest.

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": "eq_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoWindow, days, ending now.
sourceNo'usgs' (default), 'emsc' or 'irsc' (Iranian Seismological Center, latest ~20 events only).usgs
iran_onlyNoTrue: only events inside Iran (outline plus place text, incl. its waters). False: whole bounding box.
min_magnitudeNoMinimum magnitude.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.0
    • changedInput schema / properties / days / description
      Previous value: -"Window length in days, ending now, e.g. 30."New value: +"Window, days, ending now."
    • changedInput schema / properties / iran_only / description
      Previous value: -"True (default): keep only events inside a coarse Iran outline (lat/lon, includes Iranian waters) whose place text names Iran (or Persian Gulf, Gulf of Oman, Caspian Sea); neighbours across the border are dropped. False: everything in the bounding box."New value: +"True: only events inside Iran (outline plus place text, incl. its waters). False: whole bounding box."
    • changedInput schema / properties / min_magnitude / description
      Previous value: -"Minimum magnitude counted, e.g. 3.0."New value: +"Minimum magnitude."
    • changedInput schema / properties / source / description
      Previous value: -"Data source: 'usgs' (USGS ComCat, default), 'emsc' (EMSC via SeismicPortal) or 'irsc' (Iranian Seismological Center, only its latest ~20 events, with province names). Magnitudes and locations differ slightly between them; ids are not interchangeable."New value: +"'usgs' (default), 'emsc' or 'irsc' (Iranian Seismological Center, latest ~20 events only)."
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world behavior, so the description's job is lighter. It adds genuinely non-obvious context: the `truncated` flag meaning the source hit its 3000-row cap before Iran filtering, so counts reflect only the newest events — a caveat an agent could not infer from schema or annotations.

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?

Two sentences, front-loaded with the core action and outputs, followed by the truncation caveat. The truncation sentence is dense and its phrasing ('the newest') requires a moment to parse, but nothing is wasted.

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 no output schema, the description reasonably conveys what comes back (per-band and per-place counts plus the strongest event) and flags a key data-quality caveat. It stops short of describing the shape of the returned counts or how 'place' grouping is derived, but an agent can call it correctly.

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 the schema already documents days, source, iran_only, and min_magnitude with enum and bound details. The description adds little parameter-level meaning beyond the loose phrase 'over a window' and does not explain how min_magnitude interacts with the reported magnitude bands.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Count earthquakes in Iran over a window') and enumerates outputs (magnitude band, place, strongest event), which distinguishes an aggregate tool from list-style siblings. It doesn't explicitly name eq_latest or eq_search, so the separation is implied rather than stated.

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 provides a concrete usage scenario ('how active has Iran been this month'), which signals aggregation over event listing. It lacks explicit when-not-to-use guidance or a named alternative among eq_latest/eq_search/eq_significant.

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