Skip to main content
Glama

newsgurus-intel

by io.github.CollectorGuru

get_institutional_stock

[$0.1 per call] News Gurus Intel API — per-stock institutional composite for one ticker: STOCK Act congressional trades (public government disclosures) + 13F institution-holding moves (new/increased/decreased/sold from public SEC filings). Analyst-ratings and company-fundamentals numeric fields excluded (vendor licensing). 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
NameRequiredDescriptionDefault
limitNo
symbolYes

TDQS

A4/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses data source, exclusions (analyst ratings, fundamentals), educational nature, and pricing, but could add more about response format or rate limits.

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 long and includes payment details that may not be necessary for tool selection; it could be split into a pricing note and a focused functionality description. Front-loaded with purpose, but extra details add bulk.

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 data retrieval tool with no output schema, the description sufficiently explains what data is returned, exclusions, and how to access. However, it doesn't specify the structure of the response, which could be a concern, but overall adequate.

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 coverage is 0%, so description must compensate, but it only describes 'symbol' implicitly (single ticker). 'limit' is not explained, so the agent may not know it caps the number of records. This is a gap.

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 it returns per-stock institutional composite data (congressional trades and 13F moves) for a single ticker, distinguishing it from siblings like get_institutional_moves (likely broader) and get_congress_trades (congress-only).

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 implies a single-ticker scope and tells users to browse the catalog for pricing, but doesn't explicitly state when to choose this over get_institutional_moves or other siblings. It also explains payment methods, which is useful context.

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

All newsgurus-intel toolsInspect
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