Skip to main content
Glama

indonesia_search

Read-only

Paid $0.10 per call: up to 25 Indonesian articles matching a keyword, deduplicated, newest first, with source, publish time and link. Pass lang="en" to search English-language coverage of Indonesia instead.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "indonesia_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch keyword, e.g. 'suku bunga', 'rupiah', 'pertamina'. Indonesian works best.
langNoid = Bahasa Indonesia (default), en = English-language coverage of Indonesia.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / lang
      Added value: +{
      +  "description": "id = Bahasa Indonesia (default), en = English-language coverage of Indonesia.",
      +  "enum": [
      +    "id",
      +    "en"
      +  ],
      +  "type": "string"
      +}
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, but the description adds meaningful behavioral context: a $0.10 per-call cost, a 25-article cap, deduplication, newest-first ordering, and the returned fields (source, publish time, link). It does not discuss pagination, zero-result behavior, or error handling, which keeps it from a 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 with no waste: cost and core result shape are front-loaded, followed by the lang alternative. Every clause carries distinct information.

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 search tool with no output schema, the description covers cost, result count, ordering, returned fields, and the language variant. It leaves pagination or continuation behavior unstated, a minor gap given the simplicity and full schema coverage.

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%, so both parameters are already fully documented. The description reinforces the lang switch to English-language coverage, but this is already in the enum description and adds little beyond the schema; baseline 3 is appropriate.

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 and resource: search Indonesian articles matching a keyword, with scope details (up to 25, deduplicated, newest first). It does not explicitly distinguish itself from sibling tools such as indonesia_feed or indonesia_headlines, so it falls short of a 5.

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?

The keyword-matching framing implies this is the tool for targeted queries rather than browsing latest news, but the description never states when to use it versus the many sibling endpoints. The only explicit guidance is a parameter-level note to pass lang="en" for English coverage, not a usage exclusion or alternative.

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