SiteCheck Web Intel

Latest Benzinga financial news: headline, teaser, author

search_benzinga

Read-only

Latest Benzinga financial news (the public JSON feed behind benzinga.com): headline, teaser, author, time, URL, tickers, channels and tags. Filter by stock tickers (e.g. AAPL,TSLA) and/or words in the headline/teaser. Newest first, up to 100 stories; no paging into older news, no full article text. Public, no key. 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_benzinga"
  }
}

Input Schema

Name	Required	Description
`q`	No	Words that must all appear in the headline or teaser (optional, max 200 characters)
`limit`	No	How many stories, 1 to 100 (default 20)
`tickers`	No	Comma-separated stock tickers, up to 10 (optional), e.g. AAPL,TSLA

Output Schema

Name	Required	Description	Default
`q`	No
`count`	No
`source`	No
`stories`	No
`tickers`	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 readOnlyHint/openWorldHint, the description discloses the cost model in detail ($0.002 USDC per successful call, x402 on Base/Solana/Arc, failed calls not charged) and the retrieval limits (no paging, no full article text, max 100). Pricing and failure-charging behavior are exactly the kind of context annotations cannot express.

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?

A single dense paragraph that front-loads what the tool returns before covering filters, limits and price. Every clause carries information, though the parenthetical "(Base, Solana or Arc)" and repeated field lists add slight density that could be trimmed.

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 values need not be explained; annotations cover the read-only profile. What remains for an agent to call correctly — cost, payment rail, result cap, absence of paging, and filter combinations — is all present.

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 the schema already documents q, limit and tickers including the max-10 ticker cap and 1-100 range. The description reinforces the semantics ("words in the headline/teaser," "e.g. AAPL,TSLA") but adds no constraint the schema lacks, and it omits the schema's "all words must appear" AND-logic. 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?

"Latest Benzinga financial news (the public JSON feed behind benzinga.com)" names the exact verb-resource plus the underlying source, and enumerates the returned fields (headline, teaser, author, time, URL, tickers, channels, tags). An agent can distinguish this from the many other news-source siblings (search_cnbc, search_reuters_articles, etc.) purely from the description.

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 states the filter axes (tickers and/or words in headline/teaser) and the hard boundaries: "Newest first, up to 100 stories; no paging into older news, no full article text." That last clause implicitly routes the agent elsewhere for full text, though it never names a sibling alternative the way a 5 would.

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?