Skip to main content
Glama
yyordanov-tradu

stock-scanner-mcp

reddit_trending

Read-only

Scan Reddit subreddits (e.g., r/wallstreetbets, r/stocks) to retrieve trending stock tickers sorted by mention frequency. Get per-subreddit breakdown to gauge retail buzz.

Instructions

Get trending stock tickers from Reddit based on mention frequency. Scans r/wallstreetbets, r/stocks, r/investing, and r/options for posts mentioning tickers. Returns tickers sorted by mention count with per-subreddit breakdown. Limitation: uses keyword extraction (cashtags + uppercase words), not NLP — some false positives possible. Best for gauging retail buzz, not precise sentiment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subredditsNoSubreddits to scan (default: wallstreetbets, stocks, investing, options)
limitNoMaximum number of trending tickers to return (default: 20)
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true. The description adds that the tool uses keyword extraction (cashtags + uppercase words) and not NLP, allowing false positives. This disclosure of non-obvious behavior surpasses what annotations convey.

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

Conciseness5/5

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

The description is four sentences, all essential: states purpose, lists subreddits, describes return format, and notes limitations. No redundant or filler language. Efficiently front-loaded.

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?

With no output schema, the description explains that results include tickers sorted by mention count with a per-subreddit breakdown, satisfying understanding of return value. Complexity is low (two optional parameters), and the description covers usage, limitations, and output format completely.

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 100%, meaning both parameters ('subreddits' and 'limit') are already described in the schema. The description adds no new semantic information about parameters beyond what the schema provides. Baseline score of 3 is appropriate.

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 retrieves trending stock tickers from Reddit based on mention frequency, specifying subreddits scanned (r/wallstreetbets, r/stocks, r/investing, r/options) and that returns sorted tickers with per-subreddit breakdown. This distinguishes it from siblings like reddit_sentiment which focuses on sentiment analysis.

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?

The description mentions it's 'best for gauging retail buzz, not precise sentiment,' giving implicit guidance on when to use it. It also notes the limitation of false positives. However, it does not explicitly state when not to use it or name alternative tools for precise sentiment (e.g., reddit_sentiment).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yyordanov-tradu/stock-scanner-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server