Skip to main content
Glama

indonesia_snapshot

Read-only

Paid $0.05 per call: one call for the whole Indonesian picture — USD/IDR reference rate with a 30-day series, BTC/ETH/USDT in rupiah from Indodax, the latest BMKG earthquakes, upcoming national holidays and the top 5 headlines for a topic. The cheapest way to start.

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

Input Schema

NameRequiredDescriptionDefault
topicNoNews topic: nasional, dunia, finance, techno, sport, hiburan, sains, kesehatan. Default nasional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description adds value by disclosing the cost model ($0.05 per call) and the exact content bundle, which is real decision-relevant context beyond the annotations. It does not cover freshness/latency or partial-failure behavior, keeping it below 5.

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?

Two sentences, zero filler: price/scope first, content enumeration second, positioning line last. Every clause carries information an agent needs to choose or price the call.

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 one-optional-param read-only bundle with no output schema, the description is sufficient — it lists every included dataset and the cost. It could note data freshness or payload shape, but nothing required to call it correctly is missing.

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% and the schema already lists the topic values and default. The description adds the useful scoping fact that `topic` drives only the headlines section ("top 5 headlines for a topic"), clarifying that the rest of the payload is topic-independent.

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?

Names a specific composite resource and enumerates its parts: USD/IDR reference rate with 30-day series, BTC/ETH/USDT rupiah rates from Indodax, latest BMKG earthquakes, upcoming holidays, and top 5 headlines. This clearly distinguishes it from the single-purpose siblings (indonesia_fx, indonesia_crypto_idr, indonesia_earthquake, etc.).

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?

"One call for the whole Indonesian picture" and "The cheapest way to start" establish this as the entry point versus piecemeal calls, which implicitly routes against the granular siblings. No sibling is named explicitly and no when-not-to-use case is given, so it stops short of a 5.

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