Skip to main content
Glama

Gnews

by io.github.pipeworx-io

Top Headlines

top_headlines
Read-onlyIdempotent

Fetch current top news headlines from GNews (requires BYO API key). Optionally filter by category (general, world, nation, business, technology, entertainment, sports, science, health), country code, and language. Returns up to 100 articles with title, description, source, and publication date.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxNoMax articles to return (1-100, default 10)
langNoLanguage code (e.g., "en"). Default: "en"
_apiKeyYesGNews API key
countryNoCountry code (e.g., "us", "gb"). Omit for global
categoryNoNews category: general, world, nation, business, technology, entertainment, sports, science, health

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
articlesYesList of top news headlines
returnedYesNumber of articles returned in this response
total_articlesYesTotal number of top headline articles

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.5/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's mention of 'fetch' is consistent. It adds that the tool returns up to 100 articles with specific fields and requires an API key, which are useful behavioral details beyond annotations.

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, front-loaded with the main action, then filtering options, then return details. Every sentence adds value with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 100% schema coverage and the presence of an output schema, the description is complete for this simple tool. It explains purpose, parameters, and return format adequately.

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% (baseline 3). The description adds meaningful context: lists categories, explains country code omission for global, and mentions default values (max=10, lang='en'), which go beyond the schema descriptions.

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?

The description clearly states the tool fetches current top news headlines from GNews and lists filtering options, distinguishing it from sibling tools like search_news which likely perform specific searches.

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 description mentions the requirement for an API key and optional filters, providing clear context for usage. However, it does not explicitly state when to use this tool versus alternatives like search_news, so it loses a point.

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

All Gnews toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools have distinct, well-described purposes, but there is some overlap, especially among prediction market tools (bet_research, polymarket_arbitrage, etc.) and between ask_pipeworx and ask_pipeworx_grounded. Agents might occasionally select the wrong tool without careful reading.

Naming Consistency3/5

Tool names follow a mix of snake_case and camelCase (e.g., ai_visibility_check vs discover_tools). Some names are descriptive but inconsistent in style (subscribe, unsubscribe, list_subscriptions). Pattern is not uniform.

Tool Count3/5

With 32 tools, the server covers many domains (news, financials, prediction markets, entity resolution, memory). While each tool has a justification, the count feels heavy for a single server, and some tools could be consolidated.

Completeness3/5

The tool set spans a wide range of data sources and operations, but there are notable gaps. For news, only search and top headlines exist without advanced filtering. Prediction markets lack order placement tools. The broad scope means depth is sacrificed in some areas.

Resources