Skip to main content
Glama
Sign In

Agent Data Tools: Everyday data

by dev.workers.revmesh2074.agent-data-tools
OverviewDiscussionsAdmin

Earthquake data, earthquakes: list recent earthquakes worldwide from USGS, by magnitude

earthquakes
Read-only

Recent earthquakes worldwide from the US Geological Survey: magnitude, place, time, depth, coordinates, tsunami flag and USGS link, for the past day or week, filtered by minimum magnitude (2.5, 4.5 or significant). Use for alerts, news and travel checks. Example: period=day. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

Input Schema

NameRequiredDescriptionDefault
periodNohour, day (default), week or month
minMagnitudeNoSmallest magnitude to include, 0-10 (default 2.5), or significant

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / minMagnitude / description
      Previous value: -"2.5 (default), 4.5 or significant"New value: +"Smallest magnitude to include, 0-10 (default 2.5), or significant"
    • changedInput schema / properties / period / description
      Previous value: -"day (default) or week"New value: +"hour, day (default), week or month"
  2. Changed1 schema field changed
    • changedInput schema / properties / minMagnitude / type
      Previous value: -"string"New value: +[
+  "string",
+  "number",
+  "boolean"
+]
  3. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, openWorld, non-destructive and non-idempotent. The description reinforces the read-only nature and explains the billing model (first 25 free, failed calls free, each call charged), which usefully justifies the idempotentHint=false, but it omits rate limits, result caps, or ordering of returned events.

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?

Front-loaded with what the tool returns and how to filter, followed by use cases and pricing. Dense but each sentence carries information; the pricing clause is long but material to an agent deciding whether to repeat a call.

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 two-optional-parameter read tool with no output schema, the description covers source, returned fields, filters, cost and side-effect profile. Only the full set of valid periods and any result-count limits are left uncovered.

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 both parameters are already documented. The description adds example magnitude tiers (2.5, 4.5, significant), but it also narrows the period to 'day or week' while the schema allows hour and month, which adds little and slightly muddies the picture.

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 and resource (list recent earthquakes worldwide from USGS) and enumerates the returned fields (magnitude, place, time, depth, coordinates, tsunami flag, USGS link), so an agent knows exactly what it gets. No sibling tool covers seismic data, so differentiation is implicit but unambiguous.

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?

Gives concrete use contexts (alerts, news, travel checks) and a worked call example (period=day). It lacks any when-not-to-use note or mention of alternatives such as filtering by location, which is the main remaining gap.

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

All Agent Data Tools: Everyday data toolsInspect
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