Skip to main content
Glama

News headlines

news_headlines
Read-only

Search Google News for current headlines on any topic. Returns titles, sources, links, dates, and snippets. Costs $0.005 USDC per call.

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": {
      "query": "<query>"
    },
    "name": "news_headlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesNews search query (e.g. 'solana', 'AI agents', 'federal reserve')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and open-world behavior are covered. The description adds non-obvious operational context that annotations cannot express: the per-call cost of $0.005 USDC and the fields returned (titles, sources, links, dates, snippets), which is material for an agent deciding whether to spend.

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 short sentences, each carrying distinct information: what it does, what it returns, and what it costs. There is no redundant restatement of the name or title and no filler.

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?

The description covers purpose, return shape, and cost, which is largely sufficient for a one-parameter, read-only tool with no output schema. Minor gaps remain around result volume and how 'current' is defined, but nothing essential for correct invocation is missing.

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 description coverage is 100% and the single query parameter is already documented with examples ('solana', 'AI agents', 'federal reserve'). The description adds only the broad notion of 'any topic'; it gives no additional query syntax, phrase-matching, or freshness semantics. Baseline 3 applies when the schema does the heavy lifting.

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 states a specific verb and resource: 'Search Google News for current headlines on any topic.' This is clearly distinguishable from data-oriented siblings like crypto_price or on-chain tools. However, it never contrasts itself with the sibling web_search, so the boundary between general web search and news-specific search is left implicit.

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?

The phrase 'current headlines' implies usage for recent news, but there is no explicit guidance on when to prefer this over web_search, nor any statement about recency windows, result counts, or exclusions. Usage is inferable but not stated.

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