SiteCheck Crypto & Finance

Stocktwits trending stock symbols right now: ticker

finance_stocktwits_trending_symbols

Read-only

Stocktwits trending stock symbols right now: ticker, company title, exchange, watchlist count and trending score. A popularity list from social posts, not a recommendation. 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": "finance_stocktwits_trending_symbols"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	How many symbols, 1 to 30 (default 10)

Output Schema

Name	Required	Description	Default
`count`	No
`source`	No
`symbols`	No
`checkedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds substantive behavior beyond them: per-call pricing ($0.002 USDC via x402 on Base/Solana/Arc) and that failed calls are not charged. The 'not a recommendation' caveat also sets expectations about the data's nature. Missing only latency/refresh cadence 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.

Conciseness5/5

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

Two tightly written sentences, each earning its place: the first defines the resource and returned fields, the second carries the caveat and payment model. Front-loaded and free of filler.

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?

Output schema exists, so return values need not be enumerated, yet the description usefully names key fields, and the payment model is disclosed. For a one-optional-param read tool this is nearly complete; only refresh cadence/source recency is left implicit.

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% and the single 'limit' parameter is fully documented in the schema (range 1-30, default 10). The description adds no syntax or format detail beyond that, so the 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?

States a specific verb+resource ('Stocktwits trending stock symbols right now') and enumerates the fields returned (ticker, company title, exchange, watchlist count, trending score). No sibling covers Stocktwits trending data, so an agent can distinguish it immediately.

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

Usage Guidelines3/5

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

Implies usage through 'right now' and the caveat 'A popularity list from social posts, not a recommendation', which tells the agent this is a sentiment-popularity signal rather than a price or quality signal. However, it names no alternatives (e.g., finance_tradingview_ideas or finance_finviz screeners) and gives no explicit when-to-use/when-not-to-use conditions.

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

All SiteCheck Crypto & Finance 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?