newsgurus-intel

get_recent_intel

[$0.005 per call] News Gurus Intel API — most recent cross-agent market intelligence ideas (institutional flow, options flow, on-chain, news catalysts) from a 40-source SharedBrain. Optional symbol filter, up to 25 ideas per call. Educational data, not financial advice. HOW TO PAY: an x402-capable client settles the payment challenge automatically (USDC on Base, no account needed); wallet-less clients pass a subscriber API key instead (Authorization: Bearer , X-API-Key header, or ?api_key= query) for calls within their plan. Browse every tool + price first with the FREE get_catalog tool.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`symbol`	No

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations, the description carries the burden. It mentions 'Educational data, not financial advice' but does not disclose side effects, read-only nature, or any other behavioral traits. Payment method is explained, but that's not a behavioral trait.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is somewhat lengthy due to cost, payment instructions, and a reference to get_catalog, but this information is necessary for usage. It is structured in clear sentences and not overly verbose given the need to convey payment details.

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?

The description covers the data type, source, optional filters, output limit, and payment. It does not specify the output format or error handling, but for a straightforward data retrieval tool, this is sufficiently complete.

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?

The schema has two optional parameters: limit and symbol. The description explains 'Optional symbol filter' for symbol and 'up to 25 ideas per call' which implies limit's purpose. This adds meaningful context beyond the bare schema.

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 clearly states the tool's function: retrieving the most recent cross-market intelligence ideas (institutional, options flow, on-chain, news catalysts) from a 40-source SharedBrain. It distinguishes itself from siblings by emphasizing 'cross-market' and the specific source count.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives. It only suggests browsing the free get_catalog tool first, which is a general recommendation, not a specific usage condition. It does not say when to prefer this over other intel tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All newsgurus-intel tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0

Disambiguation5/5

Every tool targets a unique resource or data feed, from agent status and macro snapshots to Polymarket whale analytics and MLB props. There is no overlap or ambiguity between tools, even those within the same domain (e.g., the multiple Polymarket tools are clearly distinguished by their focus on landscape, stats, new wallets, leaders, and flagged whales).

Naming Consistency5/5

The naming follows a consistent get_<resource> pattern for all 35 data retrieval tools, with only verify_memecoin deviating but still using a clear verb-noun structure. The pattern is uniform and predictable, making it easy for an agent to infer the purpose of any tool.

Tool Count2/5

With 36 tools, this significantly exceeds the typical well-scoped range of 3-15. While the server covers a broad range of market intelligence domains, the sheer number of tools makes navigation and selection challenging for an agent, placing it in the 'too many' category.

Completeness4/5

The API provides comprehensive coverage across signals, sentiment, on-chain data, institutional activity, sports, and macro, with both broad aggregate tools and per-symbol/asset specifics. Minor gaps exist, such as a lack of direct news headlines or a fear-greed index, but these are not critical dead ends given the stated purpose of delivering derived intelligence.

Resources

Need Help?