Skip to main content
Glama

AutoTasker Hub — China Social Data API

usgs_quake

Live earthquakes worldwide from USGS: magnitude, place, depth, tsunami flag, felt reports. $0.01 USDC.

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": "usgs_quake"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
minMagnitudeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the returned field set and the cost ($0.01 USDC), which is genuinely useful behavioral context, but it says nothing about payment/auth mechanics, refresh cadence, rate limits, or what happens on upstream failure.

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

Conciseness5/5

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

Two compact sentences with the data source and field set front-loaded and pricing appended. No filler, no repetition, and nothing that could be trimmed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The enumeration of return fields partially substitutes for the missing output schema, which helps. But with no annotations and both parameters undocumented, an agent still lacks the filtering and paging semantics needed to call the tool precisely.

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

Parameters2/5

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

Schema description coverage is 0%, and the description never mentions either parameter. 'magnitude' appears only as a returned field, not as the minMagnitude filter, and the limit cap of 50 and default of 10 are left entirely to the schema.

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 names a specific resource and source: 'Live earthquakes worldwide from USGS', and enumerates the returned fields (magnitude, place, depth, tsunami flag, felt reports). That is enough for an agent to know exactly what data comes back, though it never states an explicit verb such as 'fetch' or 'list'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance appears. There is no mention of when a live global feed is preferable to a historical or regional query, and no indication that unfiltered calls return only the most recent events. The agent must infer usage entirely from the description.

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.