SiteCheck Web Intel

TechCrunch latest articles from its public RSS feed

search_techcrunch_articles

Read-only

TechCrunch latest articles from its public RSS feed (keyword filter on title/summary/tags). Headlines and excerpts only. 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_techcrunch_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 only declare readOnlyHint and openWorldHint; the description adds genuinely new behavioral facts: results are headlines and excerpts only (no full text), the feed is public and needs no key, and each successful call costs $0.002 in USDC via x402 on Base/Solana/Arc with failed calls not charged. Cost and auth disclosure is exactly the kind of context annotations cannot carry.

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 core purpose and content scope, then alternatives, then pricing. The sibling enumeration is verbose because it repeats each sibling's full title, but every sentence still carries routing or cost information.

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 values need no explanation, and the description covers content type, auth, and pricing. It omits freshness/update cadence and any note on result ordering, which would matter for a 'latest articles' 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 both parameters are already documented, making 3 the baseline. The description adds that the keyword filter matches title/summary/tags, though this slightly conflicts with the schema's 'title or summary' wording, and it says nothing about the limit parameter.

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+resource+source: latest TechCrunch articles from its public RSS feed, with the keyword filter scope on title/summary/tags. It also names the sibling tools it is not, so an agent can distinguish it from the other news-feed tools without opening a 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?

Explicitly routes to search_al_jazeera_articles and search_bbc_news_articles with the condition that selects them ('when you need ... latest articles from its public RSS feed'). It gives no guidance on when to prefer this over the many other news siblings (e.g. search_google_news, search_news_across_the_web), so the exclusion set is incomplete.

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?