Skip to main content
Glama
Sign In
GNews API MCP Server

GNews API MCP Server

by bads1de
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get-top-headlines

Retrieve top headline news articles for any category, with customizable language, country, and number of results.

Instructions

Get the latest top headline news for the specified category. Returns a list of articles including title, publication date, link, and description.

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": "get-top-headlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoNews categorygeneral
langNoLanguage code (e.g. ja, en, fr)ja
countryNoCountry code (e.g. jp, us, gb)jp
maxNoNumber of news articles to retrieve (max 10, default 5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden but only states it returns 'latest' headlines without specifying freshness, rate limits, or permissions. It fails to disclose behavioral traits beyond parameter descriptions.

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?

The description is concise with two sentences: first sentence states purpose, second describes output. No unnecessary words.

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?

Given no output schema, the description lists return fields (title, date, link, description), which is adequate. It could mention ordering or error cases, but for a headline tool, it is mostly complete.

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%, and the description adds no significant meaning beyond the parameter descriptions. It restates that 'category' is used but does not elaborate on defaults or usage.

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?

The description clearly states the verb 'Get' and the resource 'latest top headline news' and lists the returned fields. However, it does not explicitly differentiate from the sibling tool 'search-news', which would clarify its scope.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives or when not to use it. The sibling 'search-news' is not mentioned or contrasted.

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

Deploy Server

Other Tools