Skip to main content
Glama

Ezkielyna Public Tools

Gempa terbaru / Latest earthquake

gempa_terbaru
Read-onlyIdempotent

Gempabumi terbaru dari BMKG: waktu, magnitudo, kedalaman, lokasi, potensi tsunami, wilayah yang merasakan, dan link peta guncangan. Latest earthquake in Indonesia published by BMKG ("Gempabumi Terbaru"; usually M5+, can be smaller when felt). 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_terbaru"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive, so the safety profile is covered. The description adds real context beyond them: the upstream source (BMKG), the coverage quirk that events are usually M5+ but can be smaller when felt, and the absence of an API key. It does not say how fresh the data is or whether one event or a short list comes back.

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?

Front-loaded with the substantive content (what data you get) before the provenance and access notes. The bilingual duplication doubles length, but it serves the Indonesian-first audience and the Indonesian half is not a mere translation of the English half.

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?

No output schema exists, and the description compensates by listing exactly which fields come back. For a no-argument feed that is nearly enough. The one unresolved ambiguity is whether a single latest event or a short list of recent events is returned, which an agent cannot determine from the definition.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so the baseline of 4 applies; there is nothing for the description to disambiguate. The enumerated output fields are a bonus rather than a parameter explanation.

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?

States a specific resource and source: latest earthquake published by BMKG, with the returned fields enumerated (time, magnitude, depth, location, tsunami potential, felt areas, shake map link). That is far more than a restatement of the name. It stops short of naming a sibling, so an agent must infer on its own that gempa_dirasakan and gempa_m5 cover the felt-only and M5+ subsets.

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 framing: a "latest" feed, free, no key, typically M5+ but sometimes smaller when felt. That last clause hints at the overlap with the M5+ and felt-quake siblings, but the description never says when to pick those instead. Adequate for a zero-argument feed, but not explicit routing guidance.

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