SiteCheck Web Intel

Al Jazeera latest articles from its public RSS feed

search_al_jazeera_articles

Read-only

Al Jazeera latest articles from its public RSS feed (keyword filter on title/summary/categories). Latest items only. Public feed, no key. Related tools on this server, for a different need: search_techcrunch_articles when you need TechCrunch 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_al_jazeera_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/5.0

Behavior4/5

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

Annotations already mark the tool as read-only and open-world; the description adds meaningful context about public-feed/no-key access, $0.002 per successful x402 call, and no charge for failures. It omits rate limits and pagination details, but the output schema covers return values.

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?

The purpose is front-loaded and the pricing, access, and sibling-routing details are useful. The first sentence is fragmentary and the repeated 'public RSS feed' phrasing could be tightened, but the block is appropriately sized overall.

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?

For a two-parameter, read-only feed search with an output schema and annotations, the description covers source, scope, authentication, and cost. Remaining gaps such as the exact 'latest' time window and rate limits are minor.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 q and limit parameters. However, the description says the keyword filter applies to title/summary/categories while the q schema only says title or summary, which introduces a misleading parameter detail rather than reliable extra meaning.

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 resource (Al Jazeera latest articles) and mechanism (public RSS feed with keyword filtering), and explicitly distinguishes it from the TechCrunch and BBC siblings. An agent can identify the tool 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?

Explains that this is for latest Al Jazeera items only and routes the agent to TechCrunch/BBC siblings for those sources. It does not enumerate other alternatives such as article extraction or general news search, so guidance is clear but not fully exhaustive.

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?