SiteCheck Web Intel

WSJ World News headlines from the public Dow Jones RSS feed

search_wsj_articles

Read-only

WSJ World News headlines from the public Dow Jones RSS feed (latest items; keyword filter on title/summary). Headlines and short summaries only; full articles are paywalled and not returned. Public feed, no key. Related tools on this server, for a different need: search_bbc_news_articles when you need BBC News top stories from the public BBC RSS feed; search_al_jazeera_articles when you need Al Jazeera latest articles from its public 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_wsj_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 already declare readOnlyHint and openWorldHint, but the description goes further with details structured fields cannot express: no API key required, results are truncated to headlines/summaries by paywall, and crucially the x402 pricing model ($0.002 USDC per successful call, failed calls uncharged). The billing behavior is decision-relevant and would otherwise be invisible to the agent.

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 what and the data limitation before the sibling routing and pricing, and the semicolon-separated clauses keep it scannable. Slight verbosity in the repeated 'public ... RSS feed' phrasing and the fully spelled-out sibling titles, but nothing is wasted given the agent needs the price and the alternatives.

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 described, and with only two optional parameters the surface is small. Covers source, filters, data limits, cost, and alternatives — an agent could call this correctly from the description alone, with only minor residual ambiguity about freshness/latency of 'latest items'.

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%, with both q and limit fully documented including the AND-matching rule and the 1–30 range. The description's 'keyword filter on title/summary' and 'latest items' only restate what the schema already declares, so baseline 3 applies.

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 concrete verb and resource: WSJ World News headlines from the public Dow Jones RSS feed, with the scope qualifier 'latest items; keyword filter on title/summary'. It also draws the boundary that matters (headlines and short summaries only, full articles not returned), so an agent knows exactly what it gets versus a generic news search.

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 names two alternatives (search_bbc_news_articles, search_al_jazeera_articles) with the condition that selects each, which is real routing guidance rather than vague 'related tools' filler. The gap is coverage: against a sibling list containing search_nyt_articles, search_reuters_articles, search_ft_com_articles and search_google_news, the description gives no rule for choosing among same-genre newspaper feeds.

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?