Skip to main content
Glama

UK Data: News and feeds

news_search

Read-onlyIdempotent

Latest news articles on any topic, newest first, with source, date, link and summary (Bing News, GDELT as backup). For current events, company news and what is happening now. (cost: 1 credit)

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

Input Schema

NameRequiredDescriptionDefault
hoursNonumber 1-720, default 72
limitNonumber 1-100
queryNostring, required
countryNomarket, e.g. UK (default), US, IE, AU

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"e.g. UK, US"New value: +"market, e.g. UK (default), US, IE, AU"
    • changedInput schema / properties / hours / description
      Previous value: -"number 1-720"New value: +"number 1-720, default 72"
    • changedInput schema / properties / limit / description
      Previous value: -"number 1-250"New value: +"number 1-100"
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds useful behavior beyond that: results are newest-first, return source/date/link/summary, Bing News is primary with GDELT as backup, and each call costs 1 credit.

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 core purpose and return contents are front-loaded, with sourcing and cost kept in compact parentheticals. It is appropriately sized, though the parentheticals are slightly dense.

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?

For a four-parameter read-only search with no output schema, the description is nearly complete: it explains what is returned, how results are ordered, which upstream sources are used and the credit cost. Minor omissions such as pagination or result limits are already covered by the schema's limit field.

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 hours, limit, query and country are already documented in the input schema. The description adds no syntax or constraints for these parameters, which is acceptable at the baseline 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 ('news articles on any topic') plus ordering ('newest first') and return fields, so an agent immediately knows what it retrieves. It stops short of naming or differentiating from the siblings hacker_news and rss_read, which would push it to a 5.

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?

It gives clear when-to-use guidance: 'For current events, company news and what is happening now.' However, it does not state when not to use it or explicitly route to hacker_news or rss_read for alternative news sources.

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