Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

usgs_recent_earthquakes

Read-onlyIdempotent

Retrieve recent USGS earthquake data filtered by time period, minimum magnitude, and result limit to monitor seismic activity.

Instructions

Get recent earthquakes from USGS.

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_recent_earthquakes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
periodNohour, day, week, month
minmagnitudeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds no behavioral context beyond the annotations, such as data freshness, update cadence, rate limits, or default result size.

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 description is a single front-loaded sentence with no wasted text. It is appropriately concise, though its brevity contributes to the missing usage and parameter context scored elsewhere.

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

Completeness2/5

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

For a three-parameter tool with no required parameters and no output schema, the description does not explain what 'recent' means, how limit and minmagnitude affect results, or what the response contains. It is too thin to let an agent invoke the tool confidently without inspecting the schema.

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 coverage is only 33%: period has an enum description, but limit and minmagnitude are undocumented beyond their types. The description provides no parameter meaning at all, so it fails to compensate for the low schema coverage and leaves defaults and units unclear.

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 clear verb and resource: get recent earthquakes, with the source USGS. It does not distinguish this tool from siblings such as usgs_earthquake_detail or usgs_earthquakes_by_region, so an agent cannot tell from the description alone when this broad recent-quakes feed is preferable.

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?

There is no guidance on when to use this versus usgs_earthquakes_by_region or usgs_earthquake_detail. The word 'recent' implies a current-events use case, but no alternatives or exclusions are named.

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

Deploy Server

Other Tools