Skip to main content
Glama

veroq_social_trending

Get tickers and topics currently trending on social media across Reddit, Twitter, and other platforms. No parameters needed. Returns mention count, sentiment score, and hourly change for retail investor buzz.

Instructions

Get tickers and topics currently trending on social media across Reddit, Twitter/X, and other platforms.

WHEN TO USE: To discover what retail investors are buzzing about right now. No parameters needed. RETURNS: Trending symbols with name, mention count, sentiment score, and 1-hour change in mentions. COST: 20 credits. EXAMPLE: {}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Since no annotations are provided, the description carries the full burden. It discloses cost (20 credits), return fields (symbols, name, mention count, sentiment, 1-hour change), and that no parameters are needed. It does not mention rate limits or side effects, but for a read-only trending tool, this is sufficient.

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 extremely concise with a clear front-loaded purpose, followed by structured sections (WHEN TO USE, RETURNS, COST, EXAMPLE). Every sentence adds value without redundancy.

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 tool is simple with no parameters and no output schema. Description covers purpose, usage, returns, and cost. It could mention update frequency or data freshness, but it is complete enough for typical use.

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?

There are no parameters, and schema coverage is 100%, so the description doesn't need to add parameter details. It does add value by explaining the return structure, which compensates for the absence of parameters.

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 retrieves tickers and topics trending on social media platforms, with a specific verb and resource. It is distinct from siblings like veroq_trending (general trending) and veroq_social_sentiment (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 explicitly includes a 'WHEN TO USE' section, stating it's for discovering what retail investors are buzzing about, and notes no parameters needed. However, it does not mention when not to use or provide alternatives, which is a minor gap.

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/Veroq-ai/veroq-mcp'

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