Skip to main content
Glama

get_earthquakes

Read-onlyIdempotent

Get recent earthquake activity in Iceland (last 48 hours).

Returns list of earthquakes with magnitude, location, depth, and timestamp. Useful for monitoring volcanic activity and assessing travel safety.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of earthquakes to return.
min_magnitudeNoMinimum Richter magnitude. Suggested: 0 for all, 2.0 for notable, 4.0+ for significant.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the fixed 48-hour lookback window, which is a genuine behavioral fact absent from the schema. It says nothing about data source or refresh cadence, so it adds only modest value beyond the annotations.

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?

Three short lines with the scope constraint front-loaded, so the key fact is read first. The return-field listing partly duplicates the output schema and the last sentence is soft context, but neither is costly.

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?

With an output schema, full annotation coverage, and 100% schema description coverage, the definition covers the remaining gap (time window and domain relevance) adequately for a two-parameter read tool. Refresh frequency and data provider are the only notable omissions.

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?

Schema description coverage is 100%, and the schema already documents both limit and min_magnitude with suggested magnitude tiers. The description adds no syntax, bounds, or ordering meaning beyond that, so the baseline of 3 applies.

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?

States a specific verb and resource ('Get recent earthquake activity') plus explicit scope constraints: Iceland and the last 48 hours. No sibling tool covers seismic data, so an agent can select it on the resource alone without opening the schema.

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 line 'Useful for monitoring volcanic activity and assessing travel safety' implies usage contexts but never says when to prefer this over alternatives such as get_safety_alerts or get_road_conditions, nor when not to call it. Guidance is inferred rather than stated.

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.

Resources