SiteCheck Web Intel

New York Times home page headlines from the public NYT RSS

search_nyt_articles

Read-only

New York Times home page headlines from the public NYT RSS feed (latest items; keyword filter on title/summary/categories). Headlines and abstracts only. Public feed, no key. Related tools on this server, for a different need: search_ft_com_articles when you need Financial Times headlines from the public FT RSS feeds; search_wsj_articles when you need WSJ World News headlines from the public Dow Jones 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_nyt_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.6/5.0

Behavior5/5

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

Annotations only cover readOnlyHint and openWorldHint; the description adds substantial context beyond them: no API key required, a per-call price of $0.002 USDC via x402 on Base/Solana/Arc, and the important fact that failed calls are not charged. It also discloses the content ceiling ('headlines and abstracts only') and the freshness scope ('latest items').

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 purpose and scope before pricing and sibling routing, and every sentence carries information an agent needs (auth, cost, content limits, alternatives). The sibling enumeration is slightly listy but is the highest-value part of the usage guidance.

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-value explanation is unnecessary, and both parameters are fully documented in the schema. For a two-optional-parameter read-only search tool, the description covers purpose, scope, cost, auth, and alternatives — nothing material is missing.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema lacks: the keyword filter applies across title, summary AND categories (schema only mentions title/summary), and the feed returns latest items. The 'limit' behavior is left entirely to the schema, which is fine given its description.

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 description opens with a specific verb-and-resource pairing ('New York Times home page headlines from the public NYT RSS feed') and immediately scopes the content ('latest items; keyword filter on title/summary/categories', 'Headlines and abstracts only'). An agent can distinguish it from the dozens of sibling news-search tools 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 explicitly routes to alternatives with conditions: use search_ft_com_articles for FT headlines, search_wsj_articles for WSJ World News. It does not state a negative case for this tool itself (e.g., 'not for full article text' or 'not for non-NYT sources'), but the sibling routing is concrete and actionable.

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?