Skip to main content
Glama

Feegate AI Agent data marketplace catalog & platform metrics

global-seismic-activity-usgs.list_quakes

Read-onlyIdempotent

免费档:近 30 天显著地震的最前 3 条,只给震级与位置,用于确认数据口径是否合用。深度 / 时间 / 海啸标记 / 影响半径 / 官方事件链接等完整字段走 search_quakes。

[zh] 供应方资产「Global seismic activity (USGS significant, 30d)」免费(每日限额按调用方计)。 入参:无。 [en] Vendor asset "Global seismic activity (USGS significant, 30d)". Free (daily per-caller quota). Args: none. 付款/支付头在 MCP 请求头里带(X-Payment / X-Payment-Tx / Authorization: Bearer fg_…),不要放进参数。

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": "global-seismic-activity-usgs.list_quakes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior. The description goes further, disclosing the free tier with a daily per-caller quota and, importantly, that payment/auth headers (X-Payment, X-Payment-Tx, Bearer fg_…) must be sent in MCP request headers rather than parameters — actionable context not present in any structured field.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The useful content is front-loaded, but the [zh]/[en] blocks repeat the same facts in two languages, and the payment-header sentence sits after the duplication, diluting the structure. Roughly half the text is redundant restatement for an agent that only needs one language.

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, zero-argument, read-only tool with no output schema, the description covers output scope, quota, and payment mechanics. It does not specify the exact response shape or pagination, but neither is relevant given a fixed top-3 return.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero parameters, the baseline is 4; the description correctly and explicitly states '入参:无' / 'Args: none', matching the empty schema. There is nothing more to document.

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 Chinese sentence states the resource (significant earthquakes, last 30 days), the result cap (top 3), and the returned fields (magnitude and location only), and explicitly contrasts that with search_quakes for full fields. It is specific enough to distinguish from the sibling, though the English half only restates the vendor asset name rather than the operation.

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 an explicit use case — confirm the data caliber fits — and names the alternative, search_quakes, for depth, time, tsunami flags, impact radius, and official event links. It lacks an explicit 'do not use when' clause, but the routing decision is clear.

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.