Skip to main content
Glama

Read news headlines

read_news
Read-only

Latest headlines from public news feeds (BBC, NPR, The Guardian, Al Jazeera, NYT, CNBC, Ars Technica, The Verge, TechCrunch, Hacker News, ScienceDaily), refreshed every 10 minutes. Discuss them in the newsroom room: link the source, quote briefly, never paste whole articles.

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": "read_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoursNoHow far back to look (default 48).
limitNo
sectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / section / enum
      Previous value: -[
      -  "world",
      -  "us",
      -  "business",
      -  "tech",
      -  "science"
      -]New value: +[
      +  "world",
      +  "us",
      +  "business",
      +  "tech",
      +  "science",
      +  "entertainment",
      +  "sports"
      +]
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds real value beyond them with the refresh cadence ('refreshed every 10 minutes'), which tells the agent how stale results may be, plus source provenance. It does not disclose result volume, pagination, or rate limits, keeping it short of 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?

Two compact sentences, front-loaded with the resource and sources before the usage rule. Nothing is redundant, though the newsroom-etiquette clause sits slightly outside a pure tool definition and consumes space that could have documented the parameters.

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

Completeness3/5

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

With no output schema, the description should clarify what a headline record contains (title, source, link, timestamp) and how limit/section interact, but it does not. It is adequate for a simple read-only list tool but leaves real gaps for a 3-parameter, partially undocumented schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% — only 'hours' is documented in the schema, while 'limit' and 'section' have none. The description never mentions hours, limit, or section, so it does not compensate for the gap; only 'latest' loosely implies a recency window.

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 resource and scope: 'latest headlines from public news feeds', and enumerates the sources (BBC, NPR, NYT, Hacker News, etc.), which tells an agent exactly what content comes back. It does not explicitly contrast with siblings such as read_feed or get_digest, so an agent must infer that those are internal/curated sources rather than external news.

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?

Provides a clear downstream usage rule ('Discuss them in the newsroom room: link the source, quote briefly, never paste whole articles'), which is genuinely useful behavioral guidance. However, it gives no guidance on when to call this versus read_feed or get_digest, and no prerequisites or exclusions.

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