Skip to main content
Glama
Sign In
TradingView MCP

TradingView MCP

by madiver
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

pine_set_source

Injects Pine Script source code into the TradingView editor so AI clients or CLI users can update chart scripts programmatically.

Instructions

Set Pine Script source code in the editor

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": {
      "source": "<source>"
    },
    "name": "pine_set_source"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYesPine Script source code to inject

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the burden of behavioral disclosure. It states the mutating action but does not say whether existing editor content is replaced, whether compilation is triggered, whether the source must be valid Pine Script, or how errors surface. 'Set/inject' is semantically clear but leaves side effects unspecified.

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?

The description is a single, front-loaded sentence with no filler or repetition. It is efficient and easy to scan, though it is slightly under-specified in behavioral terms.

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

Completeness3/5

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

For a one-parameter mutation tool, the description plus schema is nearly sufficient. However, missing caveats about overwriting behavior, editor state requirements, and follow-up compilation leave a small but relevant gap, especially within a large sibling tool family.

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 description coverage is 100%, so the schema already documents the sole 'source' parameter. The description adds little beyond the schema's own 'inject' language, so it earns the baseline score without contributing meaningful extra parameter context.

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 clearly identifies the action ('Set') and the object ('Pine Script source code') with a specific target context ('in the editor'). It is distinguishable from read/compile/save siblings like pine_get_source, pine_compile, and pine_save, though it does not explicitly contrast with pine_save.

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 given for when this tool should be used instead of alternatives such as pine_save, pine_compile, or pine_new. Prerequisites like having an editor open or whether source should be set before compiling are not mentioned.

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