Skip to main content
Glama
Sign In

tokenguard-mcp

by io.github.eltociear
OverviewDiscussionsAdmin

earthquakes

Recent earthquakes from the USGS feed — worldwide, or within a radius of a named place. Returns magnitude, depth, tsunami flag and felt reports. (Free. This server also sells a paid API — call paid_catalogue for the routes and prices; x402 over USDC on Base, no signup.)

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

NameRequiredDescriptionDefault
daysNo1-30 days back (default 1)
limitNo1-100 events (default 20)
locationNoCentre on a place name
radius_kmNoRadius around location (default 500)
min_magnitudeNoLower bound (default 4.5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 transparency burden. It discloses the data source (USGS), the returned fields (magnitude, depth, tsunami flag, felt reports), and the free status. However, it doesn't address rate limits, error behavior, or whether the data is live, leaving some ambiguity.

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 first two sentences are efficient and directly relevant. The third sentence about the paid API is a tangential commercial note, not essential for using this tool, but it's short. Overall, it's concise but not perfectly focused.

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 simple read-only query tool with 5 self-documented optional parameters, the description covers the purpose, scope, and output content. It doesn't need to explain return format since no output schema exists, but it could mention default behavior (though schema has defaults). Overall it's sufficient.

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?

All 5 parameters are fully described in the schema (100% coverage), so the description doesn't need to add much. It does reinforce that 'location' is a named place and allows radius search, but provides no additional semantics beyond the 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 the tool retrieves recent earthquakes from the USGS feed, with options for worldwide or radius-based search. It uses a specific resource and scope, distinguishing it from sibling tools like geocode or elevation.

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?

The description gives clear context: use for recent earthquake data, either globally or near a named place. It doesn't explicitly exclude alternatives, but its distinct domain makes the usage context obvious.

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

All tokenguard-mcp 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