Skip to main content
Glama
Sign In

news

by app.vercel.indo-news-api
OverviewDiscussionsAdmin

indonesia_search_preview

Free: up to 3 Indonesian articles matching a keyword — a brand, person, place or issue (e.g. 'rupiah', 'pertamina'). Each with detected entities and an auditable sentiment score. Paid GET /search returns up to 25. Pass lang="en" to search English-language coverage of Indonesia.

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

Input Schema

NameRequiredDescriptionDefault
qYesKeyword or phrase; 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

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the free tier cap of 3 results, what comes back (detected entities and an auditable sentiment score), and the English-coverage switch. It doesn't mention auth requirements, rate limits, or what happens at zero matches, 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.

Conciseness4/5

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

Front-loaded with the most decision-relevant fact ('Free: up to 3'), and the sentences are dense but purposeful. The final sentence about lang="en" largely duplicates the enum description, a minor redundancy.

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 two-parameter read-only search with full schema coverage, an agent has everything needed: scope, result count, language behavior, and the shape of the returned data. No output schema exists, and the description adequately compensates by naming entities and sentiment, though permission/auth details are absent.

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 coverage is 100%, so both parameters are already documented in the schema. The description's notes on lang="en" and Indonesian keyword preference restate the schema almost verbatim, adding only example keywords. Baseline 3 is appropriate when the schema does all the parameter work.

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 verb and resource (search Indonesian articles by keyword) plus the exact scope (free, up to 3 results). It also distinguishes itself from the paid sibling GET /search, which returns up to 25, so an agent can tell the two apart without opening a 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?

The free-vs-paid tradeoff is laid out explicitly ('up to 3' here, 'up to 25' on paid /search), which gives a clear signal to use this as a preview. It stops short of an explicit 'use this when / avoid this when' instruction, and the paid sibling is referenced by route rather than tool name.

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

All news toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources