Skip to main content
Glama

indonesia_headlines_preview

Free: 3 latest Indonesian headlines for a topic (Google News ID edition). Pass lang="en" for English-language coverage of Indonesia. Paid full feed: GET /headlines (25 headlines).

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

Input Schema

NameRequiredDescriptionDefault
langNoid = Bahasa Indonesia (default), en = English-language coverage of Indonesia.
topicNoNews topic. Default: nasional.

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. First observed

TDQS

A4.2/5.0
Behavior4/5

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

No annotations, so the description carries the load: it discloses the free-tier cap of 3 results, the paid counterpart's 25, and the source edition (Google News ID). Missing rate-limit or return-shape detail, but the tier/quota behavior is the key fact and it is stated.

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?

Three tight sentences, front-loaded with what the tool returns and its tier, followed by the language directive and the paid alternative. Nothing redundant.

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?

With only 2 optional enum params and no output schema, the definition covers what an agent needs to call it correctly: source, result count, default topic behavior via schema, and the upgrade path. Return shape is only implied by '3 headlines', a minor gap.

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% with enum descriptions on both params, so the schema already documents defaults and values. The description restates the lang directive ('Pass lang="en" for English-language coverage of Indonesia') and adds no new syntax or semantics. Baseline 3 applies.

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+resource+scope: '3 latest Indonesian headlines for a topic (Google News ID edition)'. The 'preview' nature and free tier distinguish it from the sibling indonesia_headlines full feed 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?

Explicitly contrasts the free preview with the paid 'GET /headlines (25 headlines)' feed, giving the agent a clear escalation path. It doesn't mention the other preview-style siblings (e.g. indonesia_search_preview), so routing between similar tools is only partly addressed.

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