Skip to main content
Glama

Ezkielyna Public Tools

Gempa dirasakan / Felt earthquakes

gempa_dirasakan
Read-onlyIdempotent

Daftar 15 gempa terakhir yang dirasakan masyarakat (dengan skala MMI per wilayah) dari BMKG. The 15 most recent earthquakes felt in Indonesia, with MMI intensity by area. 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_dirasakan"
  }
}

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?

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new context: the data source (BMKG) and the absence of authentication or API key, which matters for invocation. It does not mention rate limits or response shape, but those are minor here.

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 definition is short and front-loaded, leading with the resource and scope before the access note. The Indonesian and English sentences are near-duplicates, which is mildly redundant but helps multilingual agents parse the same claim quickly.

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 read-only, two-parameter, no-output-schema tool, the description supplies the essentials: what is returned (felt quakes with MMI by region), the source, and the absence of auth requirements. The remaining gap is that it never contrasts itself with the other earthquake siblings, which a cautious agent would want.

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 (1-15, default 15) and min_magnitude (0-10) with their bounds. The description adds only the supporting fact that BMKG itself publishes just 15 recent events, which reinforces the cap but is largely redundant with the schema.

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 gives a specific verb and resource ('Daftar 15 gempa terakhir yang dirasakan masyarakat ... dari BMKG') plus the distinguishing attribute of MMI intensity by area, which separates it from a plain latest-quakes or magnitude-filtered feed. It stops short of naming a sibling such as gempa_terbaru or gempa_m5, so the differentiation is implicit rather than explicit.

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 only implied: an agent can infer this is the tool for 'felt' reports rather than magnitude-threshold feeds, but there is no explicit when-to-use or when-not-to-use statement. 'Free, no key' is an access note, not selection guidance, so the agent must reason about alternatives on its own.

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