SALT19 Agent Utility Grid

Usgs Earthquakes

usgs-earthquakes

Idempotent

Query recent USGS earthquake events by lookback window and minimum magnitude and return compact live event state. Price: $0.01 via x402. _salt19_operation_id is recommended but optional for standard x402 compatibility.

Input Schema

TableJSON Schema

Name	Required	Description
`hours`	No
`limit`	No
`min_magnitude`	No
`_salt19_handoff_id`	No	Optional SALT19 authorization handoff correlation. Preserve the same value across challenge, local signing, and paid retry.
`_salt19_operation_id`	No	Optional but recommended semantic purchase identifier preserved across challenge/payment/retries.
`_x402_payment_signature`	No	Optional x402 payment proof. Omit on the first call; include after satisfying the challenge.

TDQS

A4.1/5.0

Behavior4/5

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

The description discloses a paid invocation ('Price: $0.01 via x402'), flags the recommended SALT19 operation id for compatibility, and notes the response is 'compact live event state.' These are useful behavioral details beyond the annotations, and the readOnlyHint=false is plausibly explained by the payment side effect rather than data mutation.

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?

Three short sentences with no filler: the core query purpose is front-loaded, and the payment and compatibility guidance are isolated after it. Every sentence earns its place.

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?

With no output schema, the description should explain more about what an agent will receive; 'compact live event state' is vague about fields or format. The payment and parameter guidance is adequate, but the return-shape gap prevents full contextual completeness.

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?

The description maps 'lookback window' to hours and 'minimum magnitude' to min_magnitude, adding meaning the schema does not provide for those fields. However, it does not mention 'limit,' and the x402/SALT19 parameters are already documented in the schema, so the semantic coverage is partial rather than complete.

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 states a specific verb ('Query'), resource ('recent USGS earthquake events'), filtering criteria ('lookback window and minimum magnitude'), and return style ('compact live event state'). It is immediately distinguishable from all listed siblings, none of which cover earthquake data.

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 this when you need recent USGS earthquake events filtered by time and magnitude. It does not explicitly list when-not-to-use cases or name alternatives, but no sibling tool competes for this purpose, so the usage context is clear.

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

All SALT19 Agent Utility Grid tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0

Disambiguation2/5

Multiple tools occupy the same decision space: agent-decision-preflight, dependency-go-no-go, repo-adoption-go-no-go, github-repo-preflight, and npm-package-intel all target install/adopt GO/WARN/BLOCK decisions with overlapping scope. Discovery tools like find-salt19-tool and salt19-pricing also blur together. Descriptions are detailed, but the boundaries between these tiers are not obvious enough for reliable agent selection.

Naming Consistency3/5

Names consistently use lowercase hyphenated tokens and domain prefixes, which gives some predictability. However, styles are mixed: some tools are verb-led (find-, report-, verify-), while others are noun-headed (github-repo-facts, salt19-pricing, nws-active-alerts), and product-tier suffixes like -preflight, -facts, -intel, and -go-no-go are applied inconsistently. The naming is readable but does not follow a single clear pattern.

Tool Count2/5

33 tools is well above the range where a toolset remains easy to navigate, even for a broadly scoped utility grid. The count includes multiple free routing/telemetry tools plus many paid data and decision tools, making the surface feel heavy. A more consolidated tiered design would reduce selection burden.

Completeness4/5

The server covers a wide range of claimed capabilities: live state/facts for Base, GitHub, npm, SEC, NWS, USGS, and URL; bounded decisions for dependencies, repos, plans, code changes, and commerce; plus x402 payment support and receipt verification. Minor gaps exist around actually executing payments or settlements, but that seems intentionally out of scope for a non-custodial utility grid.

Resources

Need Help?