SiteCheck Web Intel

Latest Reuters articles: headline, publication time

search_reuters_articles

Read-only

Latest Reuters articles: headline, publication time and link, newest first, optionally matching search words, from the last 1-30 days. Found through Google News's public RSS index of reuters.com (Reuters blocks automated clients); links are Google News redirect links to the Reuters article. Headlines only, no article text. Related tools on this server, for a different need: search_ap_news_articles when you need Latest Associated Press articles: headline, publisher; search_bleacher_report_articles when you need Latest Bleacher Report articles: headline, publisher. 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_reuters_articles"
  }
}

Input Schema

Name	Required	Description
`q`	No	Optional words to search for in Reuters articles (up to 150 characters)
`days`	No	Only articles from the last N days, 1 to 30 (default 7)
`limit`	No	How many articles, 1 to 50 (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.

Changed2 schema fields changedOct 26, 2026

addedInput schema / properties / days

Added value: +{
+  "description": "Only articles from the last N days, 1 to 30 (default 7)",
+  "type": "string"
+}

changedInput schema / properties / q / description

Previous value: -"Optional words that must appear in the headline (up to 200 characters)"New value: +"Optional words to search for in Reuters articles (up to 150 characters)"

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Goes well beyond the readOnly/openWorld annotations: discloses that data comes via Google News RSS because Reuters blocks automated clients, that links are Google News redirects rather than direct Reuters URLs, that only headlines are returned with no article text, and that billing is $0.002 USDC per successful call via x402 with failures not charged. That is substantial operational context. Minor gap: no note on rate limits or how many results typically exist for a given query.

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 the purpose, then caveats (RSS proxy, redirect links, headlines only), then sibling routing, then price. Every clause carries information. Slight bloat in appending each sibling's full title phrasing ('Latest Associated Press articles: headline, publisher'), which could be trimmed.

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?

An output schema exists, so return structure need not be described, yet the description still clarifies that results are headlines only and that links are redirects — the two facts most likely to surprise a caller. Source provenance, cost model, and limitations are all present for a 3-parameter, open-world search tool.

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 all three parameters (q, days, limit) are already documented with their defaults and ranges. The description restates the same ranges ('optionally matching search words, from the last 1-30 days') without adding semantics such as how matching works or how q interacts with days. Baseline 3 is appropriate when the schema does the work.

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 and resource (latest Reuters articles), the exact fields returned (headline, publication time, link), ordering (newest first), and the retrievable window (last 1-30 days). An agent can distinguish this from the AP and Bleacher Report siblings without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: names search_ap_news_articles and search_bleacher_report_articles as the tools for other publishers' feeds, framed as 'for a different need'. Combined with the stated scope (Reuters only, last 1-30 days), when-to-use and when-to-use-something-else are both covered.

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?