Skip to main content
Glama

Agent Data Tools

by io.github.Nutshell2000
OverviewDiscussionsAdmin

Recent earthquakes, USGS data: 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. Added
  4. Removed
  5. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses pricing ($0.01/call via x402 USDC or card key), a free tier (first 25 free), failed calls free, and that repeats are charged because each call is billed. It also confirms the operation 'reads or computes only and changes nothing,' which aligns with readOnlyHint and destructiveHint 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?

The description is front-loaded with purpose and fields, then moves to use cases, an example, and billing details. It is slightly dense but each sentence adds useful information and avoids repetition.

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?

With no output schema, the description lists the key return fields (magnitude, place, time, depth, coordinates, tsunami flag, USGS link), data source, filter options, and pricing behavior. An agent has enough information to call the tool correctly and understand what it returns.

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 the schema already documents both parameters fully. The description adds an example and mentions common magnitude thresholds, but omits the schema's hour/month period options and arbitrary 0-10 magnitude range, so it provides no additional parameter clarity beyond the baseline.

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 states a specific verb and resource: list recent earthquakes worldwide from the US Geological Survey, filtered by minimum magnitude. It also names the returned fields and data source, so the agent can distinguish this from siblings like weather or country without opening the schema.

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 gives clear usage contexts (alerts, news, travel checks) and an example call. It does not state when not to use it or name a specific alternative, but the sibling tools are in unrelated domains, so the guidance is sufficient.

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 toolsInspect
Try in Browser
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources