Skip to main content
Glama

Ezkielyna Public Tools

Gempa M5+ / Recent M5+ earthquakes

gempa_m5
Read-onlyIdempotent

Daftar 15 gempa terakhir bermagnitudo 5.0 ke atas dari BMKG, dengan potensi tsunami. The 15 most recent M 5.0+ earthquakes in and around Indonesia, with tsunami potential. Free, no key.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of earthquakes to return (1-15). BMKG publishes the 15 most recent.
min_magnitudeNoOptional: only return earthquakes with magnitude >= this value.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare read-only, open-world, idempotent, and non-destructive behavior. The description adds useful context beyond that: the data source (BMKG), geographic scope (Indonesia and surroundings), the maximum of 15 results, and the availability of tsunami potential information. It does not detail return format or rate limits.

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 front-loaded with the main purpose and stays reasonably concise. The bilingual duplication is slightly redundant but serves clarity for a mixed audience; every sentence contributes some useful information.

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?

For a simple read-only list tool with two optional parameters and no output schema, the description covers the source, geographic scope, magnitude threshold, limit, and tsunami potential. It could be more complete by explaining the min_magnitude parameter's effect, but the annotations and schema compensate for most gaps.

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%, so the baseline is 3. The description reinforces the default limit of 15 and the M 5.0+ threshold, but it does not clarify how the optional min_magnitude parameter interacts with the stated M5+ baseline or explain the behavior when a lower min_magnitude is supplied.

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 specific verb (list/Daftar) and resource (15 most recent M 5.0+ earthquakes from BMKG, in and around Indonesia) and highlights tsunami potential. It implicitly distinguishes itself from broader siblings like gempa_terbaru by the magnitude filter and tsunami focus, but does not explicitly name an alternative.

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?

Usage is implied by the scope (recent M5+ quakes with tsunami potential) and the note 'Free, no key.' However, the description does not state when to prefer this tool over related siblings such as gempa_terbaru or gempa_dirasakan, nor does it include any exclusions.

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