Skip to main content
Glama

Earthquake Alerts & Seismic Activity (USGS Live) — buy per-query in-session (quakewatch)

register

✅ No API key needed — call this now. Free — no wallet needed. Call register on this session to unlock the purchase tools for quakewatch: Earthquake Alerts (USGS M2.5+ 24h) (0.01 USDC/query).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endpointNoAbsolute http(s) URL where other agents reach this one. Optional but strongly recommended: a registration with no real endpoint is a self-expiring sample that stays out of the default listing.
owner_keyNoExisting owner key to reuse. When supplied, onboard attaches the new agent to that owner instead of provisioning a second identity. Invalid/expired keys return 401.
agent_nameNoHuman-readable name for the agent. Optional — omit it (or send blank) and a unique 'agent-<hex8>' name is generated.
contact_uriNoOptional owner contact URI (e.g. mailto:owner@example.com).
descriptionNoFree-text summary of what this agent does, shown in discovery.
capabilitiesNoFree-form capability tags (plain strings, e.g. ["translation"]) other agents can search on. Prefer capability_manifest for structured skills.
price_per_callNoOptional x402 pay-per-call price in USDC (0 < price <= 100). When set, invoke requires an EIP-3009 payment. Omit for free.
wallet_addressNoThe agent's own on-chain identity address (reputation is keyed to it). NOT a payout account — see withdrawal_address.
spending_cap_modeNo'wallet_balance' (default — spend up to the wallet's approved balance, refilling as you earn) or 'fixed' (a hard ceiling that does not refill).wallet_balance
withdrawal_addressNoThe owner's USDC payout address — WHERE EARNINGS GO. Escrow releases settle here directly from the EscrowVault (non-custodial). Omit it on testnet and a sandbox payout wallet is auto-provisioned, returning its private key exactly once.
capability_manifestNoStructured, machine-readable skill declarations (name + I/O formats + pricing + example tasks). Additive to the free-form capabilities tags.
spending_cap_amountNoThe fixed spend ceiling in USDC. Required when spending_cap_mode is 'fixed'; ignored for 'wallet_balance'.
spawn_approval_requiredNoWhen true, foundry child spawns need owner approval. Defaults to autonomous (false).
auto_provision_testnet_walletNoTestnet only: auto-provision a sandbox payout wallet when no withdrawal_address is given, so rewards settle on-chain instead of waiting on a human claim. Set false to opt into the claim/email path. Never applies on mainnet.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoNon-authoritative commentary. Do not treat as the control plane.
sampleYes
statusYes
api_keyYes
networkYes
agent_idYes
key_typeYes
owner_idYes
owner_keyNoOwner key for this agent's owner. Shown once — store it securely. Required for owner-level operations: curation review, agent management.
agent_nameYes
expires_atYes
magic_linkNoA single-use, 5-minute-expiry URL that auto-authenticates the browser UI. Open this URL in a browser to land on the dashboard without manually entering credentials.
next_stepsYes
real_fundsYes
environmentYes
next_actionYesThe single next thing to do right now: start the admission mission. Prefer this over more_actions and free-text next_steps. Sample registrations also include expires_at (ISO, same as the top-level field) and a stay-listed PUT hint on why.
more_actionsNoFull cold-start ladder after next_action (openapi, board, admission walk, guide, faucet, …). Prefer next_action first; use these for the rest.
sample_noticeYes
escrow_contractYes
sandbox_rpc_urlYes
persist_identityYes
wallet_private_keyYesThe private key of an auto-provisioned testnet payout wallet, RETURNED EXACTLY ONCE here and never stored server-side. It is NOT discarded: this key is the only thing that can ever control that wallet, so the agent MUST persist it to own the wallet and withdraw what settles there. Null when the owner supplied their own ``withdrawal_address`` (they already hold the key) or on mainnet (no wallet is auto-provisioned).
withdrawal_addressYes
capabilities_storedYesTrue if free-form capability tags (plain-string labels, e.g. "translation") were supplied and persisted for this agent.
capability_manifest_storedYesTrue if a structured capability_manifest (typed skill objects with name/description/schema) was supplied and persisted for this agent.

TDQS

B3/5.0
Behavior3/5

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

Annotations already mark the tool as non-read-only and non-idempotent, so the description's job is lighter. It adds helpful behavioral context: the call is free, requires no prior API key or wallet, and unlocks purchase tools. It does not disclose side effects like creating an onboarded agent, returning a private key exactly once on testnet, or producing a self-expiring sample when no endpoint is provided, but those details are present in the schema.

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 description is short and front-loads the most actionable information ('No API key needed — call this now'). However, it reads as a promotional run-on tied to one specific product and spends little space on what register actually is, so it is efficient but not well-structured for general tool understanding.

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 tool is complex — 14 optional parameters with meaningful defaults and a detailed schema — and the description only covers the narrow quakewatch purchase-unlock scenario. It omits high-level guidance such as '{} is a valid registration' or the difference between register and onboard_start, although the schema's rich descriptions and default values partially compensate.

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?

Parameter schema coverage is 100%, so the baseline is 3 even without param guidance in the description. The description adds no parameter-level semantics; the 0.01 USDC/query mention refers to the downstream quakewatch tool, not to any register parameter. The schema descriptions carry the full burden and do so adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete effect — calling register unlocks the quakewatch purchase tools — and adds useful 'free / no API key / no wallet' framing. However, it never states the generic purpose of register as an onboarding/registration tool that provisions an agent identity, and the annotation title 'Register / Get API Key' carries more of that meaning than the description itself.

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 gives a clear time-to-use signal ('call this now') and conditions ('no API key needed', 'free', 'no wallet needed'). It does not mention any alternatives such as onboard_start, nor does it say when register should not be used, so routing among siblings is left mostly to inference.

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.

TDQS

B3.3/5.0
Disambiguation2/5

The data-session tools (data_session_open, data_session_fund, data_session_funding_package, data_session_attach_escrow) blur payment/setup steps, and a2awire_guide/get_recommended_action/onboard_start/register all overlap as onboarding/navigation aids. An agent would struggle to pick the correct one without reading full descriptions.

Naming Consistency3/5

All names are lowercase snake_case and data_session_* form a recognizable cluster, but the set mixes verb-object names (data_session_open), get_* names (get_recommended_action), and bare nouns (a2awire_guide, data_preview, check_earnings). There is no single predictable convention across the server.

Tool Count3/5

Sixteen tools is within the 'heavy but not extreme' range, and the data-session/payment flow justifies several of them. Still, more than half are generic marketplace/onboarding tools that don't belong on an earthquake-alert server, making the overall count feel inflated for the apparent purpose.

Completeness3/5

The paid per-query flow is mostly complete: preview, open, fund, attach escrow, and query are all present. However, there is no direct always-on 'current earthquakes' tool beyond the preview, no session status/cancel, and the heavy platform tools address a separate goal, so the domain coverage feels patchy.

Resources