SiteCheck Crypto & Finance

TradingView public trading ideas: the latest published idea

finance_tradingview_ideas

Read-only

TradingView public trading ideas: the latest published idea titles and their chart links, read from the public ideas page. Community opinions, not investment advice; no prices are computed. Related tools on this server, for a different need: finance_tradingview_screener when you need TradingView stock screener results for one market: symbol. 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_tradingview_ideas"
  }
}

Input Schema

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

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Goes beyond the readOnly/openWorld annotations by disclosing the pay-per-call model ($0.002 USDC per successful call via x402, failures not charged) and clarifying that no prices are computed and the content is unvetted community opinion. This is genuine decision-relevant behavior an agent would otherwise not know.

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

Conciseness4/5

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

Front-loaded with the core purpose and the disclaimer before routing and pricing details. The pricing sentence is dense but materially useful; overall there is little wasted wording, though the paragraph is long for a one-parameter tool.

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?

With an output schema and annotations already present, the description covers what the tool returns conceptually, the safety profile, cost, and the sibling alternative. The only gap is the recency semantics behind 'latest' and whether results are paginated, which a caller might want to know.

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 already documented with its 1–30 range and default of 10. The description adds no further meaning about ordering, recency window, or what 'latest' means in practice, so the baseline 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 and resource: it reads the latest published TradingView idea titles and their chart links from the public ideas page. It also scopes what the data is not (community opinions, no computed prices), which tells an agent exactly what it is getting.

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?

Explicitly routes to finance_tradingview_screener 'when you need TradingView stock screener results for one market: symbol', giving a clear alternative and the condition that selects it. It stops short of stating exclusions for this tool (e.g. that it cannot filter by symbol), so it's strong but not exhaustive.

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?