Skip to main content
Glama

BRAINIAC Geo & Environment Lookups

Query USGS earthquakes nearby

geo-environment_earthquake-query
Read-onlyIdempotent

Find earthquakes within a radius and time window from the vendored USGS all_month feed. Price $0.03 USDC. POST /api/v1/geo-environment/earthquake-query. An unpaid call returns the x402 payment terms and does not run.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>",
      "radiusKm": "<radiusKm>"
    },
    "name": "geo-environment_earthquake-query"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoto, string, length 10 to 40. Optional.
fromNofrom, string, length 10 to 40. Optional.
sortNosort, string, one of time, magnitude. Required.time
limitNolimit, integer, from 1 to 500. Required.
latitudeYeslatitude, number, from -90 to 90. Required.
radiusKmYesradiusKm, number, from 1 to 20000. Required.
eventTypeNoeventType, string, length 1 to 40. Required.earthquake
longitudeYeslongitude, number, from -180 to 180. Required.
minMagnitudeNominMagnitude, number. Optional.

Output Schema

NameRequiredDescriptionDefault
countNocount. Number.
eventsNoevents. Array.
windowNowindow. Object.
sourcesNosources. Array.
snapshotAtNosnapshotAt. String.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral facts not in the annotations: a fixed price of $0.03 USDC and the failure mode that an unpaid call returns x402 payment terms rather than executing — exactly the kind of pre-call behavior an agent needs. It does not mention result caps or pagination beyond the limit parameter.

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?

Three short sentences, with the core purpose front-loaded and each subsequent sentence carrying distinct information (data source, price, endpoint, payment semantics). The raw endpoint path is the least valuable element but is brief enough not to be wasteful.

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?

For a nine-parameter read tool with a full schema, exhaustive parameter documentation, and an output schema, the description supplies what structured fields cannot: the data source, cost, and the x402 unpaid-call behavior. Only minor gaps remain, such as whether results are freshly synced or how the 'all_month' window interacts with the user-supplied from/to range.

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 description coverage is 100%, so every one of the nine parameters is already documented in structured form; the baseline of 3 applies. The description adds only the conceptual mapping of 'radius' and 'time window' to radiusKm and from/to, with no formats, defaults, or interaction between filters such as minMagnitude and sort.

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 gives a specific verb and resource ('Find earthquakes within a radius and time window') and names the underlying data source ('vendored USGS all_month feed'), which keeps it clearly distinct from sibling tools like fire-hotspots-nearby or sun-times-position. It stops short of explicitly contrasting itself with any alternative, which is the only thing separating it from a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrases 'within a radius and time window' imply the query shape and therefore the usage context, and the payment note warns of a precondition before a call succeeds. However, there is no explicit when-to-use vs when-not guidance and no routing to alternatives for broader or unfiltered event queries.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources