Crypto, web, finance and app data tools

Recent Earthquakes

earthquakes

Recent earthquakes worldwide or within a radius of a point (USGS): magnitude, place, time, depth, tsunami flag, PAGER alert and felt reports, over the last hour, day, week or month. Use for risk monitoring and news.

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

Input Schema

Name	Required	Default
`lat`	No
`lon`	No
`limit`	No
`period`	No	day
`radius_km`	No
`min_magnitude`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 22, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the upstream source (USGS) and the result fields, but says nothing about defaults (limit=50, period=day, radius_km=500, min_magnitude=4.5), rate limits, or what happens when lat/lon are omitted or only partially supplied. That is a meaningful gap for a six-parameter query tool.

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 dense sentences, zero filler, and the core capability plus data source are front-loaded ahead of the usage hint. Every clause carries information an agent cannot get from the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return-value detail is not required, yet the description spends words on fields while leaving four of six parameters' defaults and semantics undocumented. For a tool with zero schema coverage and no annotations, that leaves an agent guessing at filter behaviour.

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 0%, so the description must compensate. It does add real value for `period` by enumerating hour/day/week/month (the schema has no enum), and it explains that radius works around a point. But `limit` and `min_magnitude` are never mentioned, and the lat/lon pairing rule is only implied.

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?

States a specific verb+resource (recent earthquakes), names the data source (USGS), the two search modes (worldwide or radius around a point), the fields returned (magnitude, place, time, depth, tsunami flag, PAGER alert, felt reports) and the supported time windows. No sibling tool overlaps this domain, so differentiation is trivially achieved.

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?

"Use for risk monitoring and news" gives a clear intended context and the two modes of use (worldwide vs. radius) are spelled out, but there are no exclusions, no prerequisites (e.g. that lat/lon must be supplied together for a radius query) and no guidance on choosing a period.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crypto, web, finance and app data tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?