mcp-gempa-bmkg

gempa_dirasakan

Retrieve recent felt-earthquake reports and filter by minimum magnitude to identify significant events affecting residents.

Instructions

Daftar gempa yang dirasakan warga (maks. 15 terbaru), bisa difilter magnitudo minimum.

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

Input Schema

Name	Required	Description	Default
`min_magnitudo`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 8, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description must carry the full burden. It usefully discloses a hard result cap (15) and recency ordering, which matters for interpreting output, but says nothing about the data source, freshness window, or what happens when nothing matches the magnitude filter.

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?

A single front-loaded sentence with no filler; the scope and cap come first. It is perhaps terse to the point of omitting the sibling distinction, but nothing in it is wasted.

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?

This is a simple one-parameter read tool, and an output schema exists so return values need not be explained. The description covers listing, cap, ordering and filtering, leaving only the sibling differentiation and data-source/freshness context unaddressed.

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 0% for the single parameter, so the description must compensate. It clarifies that min_magnitudo acts as a lower-bound filter on a magnitude scale, which adds a little meaning beyond the bare property name, but omits units/range and interaction with the default of 0.

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 verb+resource ('Daftar gempa yang dirasakan warga') plus the two defining limits: max 15 results and newest-first ordering. It does not explicitly contrast with the sibling gempa_terkini, so the felt-vs-recent distinction 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?

No when-to-use / when-not guidance and no reference to the sibling gempa_terkini, which is the only real alternative for earthquake listings. The magnitude filter is mentioned, but that is parameter behavior, not tool selection guidance.

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

Deploy Server