SiteCheck Web Intel

Defector articles from its public RSS feed

search_defector_articles

Read-only

Defector articles from its public RSS feed (keyword filter on title/summary/tags). Latest items only; excerpts are as published in the feed. Public feed, no key. Related tools on this server, for a different need: search_al_jazeera_articles when you need Al Jazeera latest articles from its public RSS feed; search_bbc_news_articles when you need BBC News top stories from the public BBC 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_defector_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.1/5.0

Behavior4/5

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

The annotations only declare readOnlyHint and openWorldHint, and the description adds substantial context beyond that: no API key required, only latest items, excerpts are verbatim as published, and a metered cost of $0.002 USDC per successful call via x402 on Base/Solana/Arc with failed calls uncharged. That payment and freshness behavior is exactly the kind of thing an agent cannot infer from the annotations. Rate limits or result-freshness windows are not specified.

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?

Scope and filtering constraints are front-loaded in the first two sentences, with pricing last, which is the right ordering. The sibling-differentiation sentence is long and somewhat repetitive in phrasing ("when you need ... from its public RSS feed"), costing a little tightness.

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?

With an output schema present, return-shape explanation is unnecessary, and the description covers the remaining essentials: data source, freshness limit, auth model, and cost. Only minor gaps remain, such as how the two parameters interact when q is omitted and the tags-versus-summary mismatch with the schema.

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 coverage is 100%, so the schema already documents both parameters, and the description's "keyword filter on title/summary/tags" only loosely echoes it — notably it mentions tags while the schema says title or summary, a small inconsistency. No extra syntax or matching-rule detail is added beyond the schema's "must all appear" wording, 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?

The definition names a specific resource (Defector articles from its public RSS feed) plus the retrieval constraint (keyword filter, latest items only), and explicitly distinguishes itself from the two named sibling news-feed tools. An agent can identify what it returns 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?

It states the selection condition for the two named alternatives ("when you need Al Jazeera latest articles" / "BBC News top stories"), which effectively tells the agent when to pick this tool instead. It stops short of stating when NOT to use it (e.g. historical/archive lookups), and many other sibling news feeds are left undifferentiated.

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?