Skip to main content
Glama
Sign In
tradinview-mcp

tradinview-mcp

by Ham12-3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Render chart HTML

render_chart_html

Generates interactive HTML charts from candlestick data and optional technical indicators using TradingView Lightweight Charts.

Instructions

Render safe local HTML using TradingView Lightweight Charts and caller-provided data.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>",
      "bars": "<bars>"
    },
    "name": "render_chart_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes
barsYes
indicatorsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are provided, so the description must fully convey behavioral traits. It only says 'safe local HTML' without explaining side effects, permissions, or whether it is read-only. It does not disclose any limitations or state changes.

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

Conciseness2/5

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

The description is extremely brief (one sentence) but lacks essential detail. It is under-specified rather than efficiently informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (3 parameters including optional indicators) and lack of output schema, the description is severely incomplete. It fails to explain return values (e.g., rendered HTML) or how to interpret results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% (no property descriptions in schema) and the description does not mention any parameters. The agent must rely solely on names and schema types, which are insufficient for understanding data formats and constraints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description includes the verb 'Render' and identifies the resource as 'safe local HTML using TradingView Lightweight Charts and caller-provided data'. The name and context clearly distinguish it from sibling tools (watchlists, quotes, searches).

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives or when not to use it. There is no mention of prerequisites or exclusions.

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

Deploy Server

Other Tools