SiteCheck Web Intel

PR Newswire health-category press releases from its public

search_prnewswire_press_releases

Read-only

PR Newswire health-category press releases from its public RSS feed (keyword filter on title/summary). Latest items only. Public feed, no key. Related tools on this server, for a different need: search_doj_press_releases when you need US Department of Justice press releases; search_press_release_multi_wire when you need latest press releases merged from public wire feeds: PR. 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_prnewswire_press_releases"
  }
}

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.4/5.0

Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses that the feed is public and keyless, that only the latest items are returned, and the exact payment model (x402, $0.002 USDC per successful call, no charge on failure). Cost and billing behavior is the kind of detail annotations never carry, and it is spelled out here.

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 source and scope, then alternatives, then price — a sensible order with no filler. The lead-in phrase 'Related tools on this server, for a different need:' is slightly wordy for what follows.

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 shape need not be described, and the description covers the remaining decision-critical facts: source, category, freshness limit, auth (none), cost, and alternatives. Nothing an agent needs to call this correctly is missing.

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 both q and limit are already documented including the 'all words must appear' semantics and the 1–30 range. The description's 'keyword filter on title/summary' restates rather than extends the schema, so the 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 specific verb and resource: press releases from PR Newswire's public RSS feed, narrowed to the health category, with keyword filtering on title/summary. An agent can immediately tell this is a niche, source-specific news lookup rather than a general web 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 routes the agent elsewhere for DOJ releases and for merged multi-wire results, and adds the 'latest items only' scope constraint. The one gap is that the nearest sibling, search_pr_newswire (presumably a broader PR Newswire search), is never mentioned, so an agent could pick this health-limited tool when a general one was wanted.

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?