Skip to main content
Glama

Feegate AI Agent data marketplace catalog & platform metrics

global-seismic-activity-usgs.search_quakes

Read-onlyIdempotent

按最小震级筛选显著地震并返回完整字段:震级、位置、深度、发生时间、海啸标记、影响强度 sig、数据来源网络、官方事件详情页链接,可直接用于灾害风险评估。

[zh] 供应方资产「Global seismic activity (USGS significant, 30d)」按次计费 $0.09 USDC(或等值积分)。 入参:min_mag。 [en] Vendor asset "Global seismic activity (USGS significant, 30d)". Paid per call: $0.09 USDC (or prepaid credits). Args: min_mag. 付款/支付头在 MCP 请求头里带(X-Payment / X-Payment-Tx / Authorization: Bearer fg_…),不要放进参数。

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": {
      "min_mag": "<min_mag>"
    },
    "name": "global-seismic-activity-usgs.search_quakes"
  }
}

Input Schema

NameRequiredDescriptionDefault
min_magYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / min_mag
      Added value: +{
      +  "title": "Min Mag",
      +  "type": "number"
      +}
    • removedInput schema / properties / q
      Removed value: -{
      -  "title": "Q",
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "q"
      -]New value: +[
      +  "min_mag"
      +]
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so safety is covered. The description adds substantial value beyond that by disclosing a per-call charge of $0.09 USDC, the vendor asset identity, and exact authentication mechanics: payment headers travel in the MCP request (X-Payment, X-Payment-Tx, Authorization Bearer), not in the args. It also lists returned fields, compensating for the missing output schema, though rate limits and result caps are not mentioned.

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 structure is sensible: purpose and return fields first, then payment and auth mechanics, then the parameter warning. The field enumeration is dense but useful given no output schema. The bilingual duplication adds some length, but it is purposeful for language coverage rather than filler.

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 single-parameter, read-only, no-output-schema tool, the description covers what an agent needs: what the call returns, that it costs money, and how to authenticate. The fixed 30-day window appears only inside the asset title rather than the prose. The main residual gap is the absent numeric domain for min_mag.

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?

With 0% schema description coverage and one parameter, the description carries the burden: it names min_mag and its selection semantics, which adds meaning over the bare schema property. However, no numeric range, unit, or example threshold is given, so an agent still cannot confidently choose a value. The statement that payment headers remain outside parameters is the most useful schema-adjacent clarification.

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 states a specific verb and resource combination: filtering significant earthquakes by minimum magnitude, within the 30-day window named in the asset title. It also enumerates the returned fields (magnitude, location, depth, time, tsunami flag, sig, source network, event detail URL), which clarifies scope well. It does not distinguish itself from the sibling list_quakes, so an agent cannot tell from the description alone which one to pick.

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 description frames the call as a magnitude-threshold screen usable for hazard risk assessment, which implies the when-to-use context. The phrase 按最小震级筛选 implies a filtered-dataset call rather than a full listing, hinting at the list_quakes split, but no explicit alternative or exclusion is named. This is implied guidance, not explicit routing.

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.