Skip to main content
Glama
Sign In
quake-mcp

quake-mcp

by adamcwade
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get earthquake details

get_earthquake

Retrieve complete details for a specific earthquake using its USGS event ID, including magnitude, location, depth, time, felt reports, intensity, PAGER alert, tsunami flag, and link to the USGS event page.

Instructions

Get full details for a single earthquake by its USGS event id (e.g. us7000abcd, returned by the search tools). Includes magnitude, location, depth, time, felt reports, intensity, PAGER alert level, tsunami flag, and a link to the USGS event page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "event_id": "<event_id>"
    },
    "name": "get_earthquake"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYesUSGS event id, for example us7000abcd or nc73649170.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

No annotations provided. Description lists returned fields but does not mention any side effects, rate limits, or authentication needs. Reasonable but not exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no redundancy. Purpose and details are front-loaded. Efficient.

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?

For a single-parameter tool with no output schema, the description fully informs the agent about input requirements, output contents, and tool purpose.

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

Parameters4/5

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

Schema covers event_id 100%. Description adds an example and explains the id source (from search tools), providing value beyond 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 clearly states it gets full details for a single earthquake by USGS event id. It distinguishes from sibling tools (search, count, recent).

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?

Mentions the id is returned by search tools, implying prior use of search. Lacks explicit when-not-to-use or alternatives, but context is clear.

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