chartink-query

Chartink Query Builder

Generate valid Chartink scan_clause strings from a plain-English description of what to screen for, then (optionally) validate and run them via the chartink MCP server.

What a Chartink scan_clause looks like

A scan clause is a single string with this overall shape:

( {segment} ( <condition> [and|or <condition>] ... ) )

• The outer ( ... ) and {segment} are mandatory. Default segment is {cash} (all NSE cash stocks).
• Conditions are joined with lowercase and / or. Group with extra nested parentheses to control precedence.
• Every token is lowercase. Spaces around operators, commas, and parentheses are expected — write sma( latest close , 50 ), not sma(latest close,50).

A condition is built as:

[timeframe] [attribute-or-indicator] [comparison-operator] [timeframe] [value-or-indicator]

Examples:

( {cash} ( latest close > latest sma( latest close , 50 ) ) )

( {cash} ( latest rsi( 14 ) > 60 and latest close > 1 day ago close ) )

( {cash} ( latest close > latest open and latest volume > latest sma( latest volume , 20 ) and latest close > 50 ) )

Always output BOTH forms

Every time you produce a query, give the user two versions side by side:

1. MCP / API form (run_screener scan_clause) — the fully wrapped string including segment:

   ( {cash} ( latest close > latest sma( latest close , 50 ) ) )
   

2. Chartink.com form (paste into the Scan conditions box at chartink.com/screener) — the inner conditions only, no outer ( {cash} ( ... ) ) wrapper, since the segment is chosen from the page's dropdown:

   latest close > latest sma( latest close , 50 )
   

   Also state which segment dropdown to select (e.g. "Cash" for {cash}, "Intraday" for an intraday timeframe).

The two are the same conditions — the only difference is that the MCP form wraps them in ( {segment} ( ... ) ) and the website supplies the segment via its UI. Label each clearly so the user knows which to use where.