Skip to main content
Glama

indonesia_earthquake

Read-only

Paid $0.05 per call: the latest official BMKG earthquakes — magnitude, depth, coordinates, region, tsunami potential, felt reports and the official shakemap URL. Up to 15 recent events. With alert=true it returns a decision instead of a feed: alert true/false for minMagnitude (default 5 SR) among the events checked, the matching events and a 180s poll hint — the shape a risk or logistics poller acts on, same upstream call, no extra charge. Without alert= minMagnitude filters the feed itself, before limit is taken.

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

Input Schema

NameRequiredDescriptionDefault
alertNotrue = decision view: alert true/false for the threshold below, plus the matching events.
limitNoNumber of recent events, 1-15. Default 5.
minMagnitudeNoAlert threshold in SR (BMKG Magnitudo). Default 5.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / alert
      Added value: +{
      +  "description": "true = decision view: alert true/false for the threshold below, plus the matching events.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / minMagnitude
      Added value: +{
      +  "description": "Alert threshold in SR (BMKG Magnitudo). Default 5.",
      +  "type": "number"
      +}
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond readOnlyHint=true by disclosing the $0.05 per-call price, that the alert mode incurs no extra charge, a 180s poll hint, the 15-event cap, and the ordering rule that minMagnitude filters before limit is applied. These are the operational facts an agent needs to budget calls and interpret results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Pricing and the resource come first, then the feed description, then the alert-mode delta and the filter ordering — a logical front-loaded order. Dense punctuation but no sentence is filler; each clause carries cost, output shape, or semantics.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-value burden and does so: it names every feed field and the contents of the decision view (verdict, matching events, poll hint). Combined with defaults and the 15-event bound, an agent could call this correctly with no further information.

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?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning the schema lacks: minMagnitude changes role depending on alert (threshold for the decision vs. a pre-limit feed filter), and the 5 SR default is reinforced in context. The interaction between the three parameters is genuinely clarified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (latest official BMKG earthquakes) and enumerates the returned fields — magnitude, depth, coordinates, region, tsunami potential, felt reports, shakemap URL. It also spells out the two output shapes (feed vs. decision), so an agent knows exactly what it gets without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly contrasts the two modes: alert=true yields a decision for polling, no alert yields a filtered feed, and it names the intended consumer ('a risk or logistics poller acts on'). No sibling alternatives are named, but the sibling list contains no overlapping earthquake tool, so there is little to disambiguate.

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