SiteCheck Web Intel

BBC News top stories from the public BBC RSS feed

search_bbc_news_articles

Read-only

BBC News top stories from the public BBC RSS feed (latest items; keyword filter on title/summary). Headlines and summaries only, no full article text. Public feed, no key. Related tools on this server, for a different need: search_ap_news_articles when you need Latest Associated Press articles: headline, publisher; search_wsj_articles when you need WSJ World News headlines from the public Dow Jones RSS feed. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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

Input Schema

Name	Required	Description	Default
`q`	No	Words that must all appear in the title or summary (optional, max 200 characters)
`limit`	No	How many items, 1 to 30 (default 10)

Output Schema

Name	Required	Description	Default
`q`	No
`count`	No
`items`	No
`source`	No
`checkedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds materially new behavior: results are headlines/summaries only with no full article text, the feed is public with no key required, and each successful call costs $0.002 USDC via x402 on Base/Solana/Arc while failed calls are free. Cost and payment-rail disclosure is exactly the kind of operational fact an agent cannot get from structured fields.

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?

Front-loaded with purpose, then content limits, then sibling routing, then pricing — a sensible ordering with no filler. The sibling enumeration and payment sentence make it longer than strictly necessary, but each clause carries usable information.

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?

An output schema exists, so return shape need not be explained, and both parameters plus pricing and content limits are covered. Minor gaps remain: no statement of result ordering beyond "latest," and no mention of rate limits or what an empty match returns.

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 schema already defines both parameters including the AND-semantics of `q` and the 1-30 range of `limit`. The description only restates the keyword filter on title/summary and adds the notion of "latest items," which is marginal value over the schema. Baseline 3 is appropriate.

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?

States a specific verb+resource (top stories from the public BBC RSS feed), scopes content explicitly ("headlines and summaries only, no full article text"), and names the sibling tools it is not (search_ap_news_articles, search_wsj_articles). An agent can distinguish this from the many other news tools without opening the schema.

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?

Explicitly routes to search_ap_news_articles and search_wsj_articles "for a different need," giving clear alternative selection logic. It does not address when this source is preferable over the broader aggregators in the sibling list (e.g. search_google_news, search_news_across_the_web), so exclusion guidance is partial rather than complete.

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

All SiteCheck Web Intel tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?