mcp-gempa-bmkg

gempa_terkini

Retrieve the current single earthquake event in Indonesia from BMKG data, including location, magnitude, and time details for situational awareness.

Instructions

Gempa terbaru (satu kejadian) di Indonesia, dari data BMKG.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 8, 2026

TDQS

B3.3/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the disclosure burden. It usefully reveals the upstream source (BMKG) and that exactly one event is returned, but says nothing about data freshness/refresh cadence, rate limits, or what happens when no recent event exists. For a simple zero-parameter read this is acceptable but not rich.

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?

One short sentence with no wasted words, and the key qualifiers (one event, Indonesia, BMKG) are front-loaded. It is efficient rather than padded, though it is terse enough to feel like a bare label.

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?

An output schema exists, so return structure need not be explained, and zero parameters remove most input ambiguity. Still missing is any statement about recency definition (most recent by origin time?) or behavior on an empty result, which matters for a 'terkini' tool.

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 zero parameters, so there is no parameter meaning to add; baseline 4 applies. The description's only relevant semantic contribution is clarifying that the result set is a single event rather than a list.

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 cardinality: the single latest earthquake event ('satu kejadian') in Indonesia, sourced from BMKG. That is clear enough for an agent to know what it fetches, but it never names the sibling gempa_dirasakan, so the boundary between 'latest' and 'felt' earthquakes is left implicit.

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 when-to-use / when-not-to-use guidance and no reference to the alternative tool gempa_dirasakan. The agent must infer from the noun phrase alone that this is the right call for a current-quake lookup versus a felt-quake lookup.

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

Deploy Server