Skip to main content
Glama

News headlines, latest news: search current news articles (Brave)

news
Read-only

News headlines on any topic, crypto included, as JSON: title, URL, snippet, publisher domain and age, from the Brave Search API's news index. 1-20 results per call; freshness limits results to the past day, week or month. Results are for the caller's immediate use only: no storing, resale or model training (Brave API terms). Upstream failures return 503, uncharged. Use when an agent needs current news on a topic. Example: q=bitcoin ETF. Price $0.01/call via x402 USDC or a card key (/credits); failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": {
      "q": "<q>"
    },
    "name": "news"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesNews search query, at most 400 characters
countNoNumber of results (1-20, default 10)
freshnessNoOnly articles from the past day, week or month (default: any age)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / count / maximum
      Previous value: -9007199254740991New value: +20
    • changedInput schema / properties / count / minimum
      Previous value: --9007199254740991New value: +1
  2. Added

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations (readOnly, openWorld, non-idempotent, non-destructive), the description discloses result limits, freshness behavior, upstream 503 handling with no charge, per-call pricing and the fact that repeats are not free, plus Brave's no-storage/no-resale/no-training terms. The charge-on-every-call note also explains why the annotation marks the tool non-idempotent.

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?

The lead sentence front-loads what the tool does and what it returns, followed by limits, licensing, pricing and safety in a compact block. It is dense and slightly crowded with commercial terms, but almost every sentence carries information an agent needs before calling a paid tool.

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?

With no output schema, the description compensates by enumerating the return fields (title, URL, snippet, publisher domain, age) and covers cost, failure mode and usage restrictions. For a three-parameter, read-only search tool that is sufficient to call it correctly.

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%, so the baseline is 3. The description restates the 1-20 count and the day/week/month freshness values already present in the schema, and adds an example q value; it does not add syntax, quoting, or query-operator details beyond what the schema provides.

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 names a specific verb and resource: retrieve news headlines on any topic, as JSON, from the Brave Search API's news index, with the returned fields listed. It distinguishes itself from the generic 'search' sibling by emphasizing the news index and current articles, though it never names an alternative tool explicitly.

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?

It says 'Use when an agent needs current news on a topic' and supplies an example query, which gives clear positive guidance. There is no when-not guidance and no routing to sibling tools such as search or domain, so the agent must infer that this is not the tool for general web or company research.

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.