Skip to main content
Glama

Look up a TradingView name

migration_lookup
Read-onlyIdempotent

What a name of TradingView's charting library (Advanced Charts, Trading Platform) or Lightweight Charts becomes in TradeCanvas: a widget option, featureset, override key, study, drawing shape, widget or chart method, datafeed or broker…

Instructions

What a name of TradingView's charting library (Advanced Charts, Trading Platform) or Lightweight Charts becomes in TradeCanvas: a widget option, featureset, override key, study, drawing shape, widget or chart method, datafeed or broker member, or a resolution. Gives the TradeCanvas option, feature switch, style key, indicator id (with its defaults and line keys), drawing type (with its anchors) or call, and says plainly when there is no equivalent and what to do instead. Look up one name with 'name', or search the table with 'query'.

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": "migration_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoWhat the name is: a widget 'option', a 'featureset', an 'override' key, a 'study' (indicator), a 'drawing' (shape name), a 'method' of the widget or a chart, a 'datafeed' or 'broker' member, or a 'resolution' ('60', '1D').
nameNoThe name as the old library spells it: 'header_widget', 'paneProperties.background', 'Relative Strength Index', 'trend_line', 'createStudy', 'getBars', '60'.
queryNoWords to find in the table's names, targets and notes, when there is no exact name: 'volume', 'legend'.
sourceNoThe library the app uses now: 'tradingview' (Advanced Charts, Trading Platform; the default) or 'lightweight-charts'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.13.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, and non-destructive, so safety is covered. The description adds real substance beyond that: it discloses the shape of the result (option, feature switch, style key, indicator id with defaults and line keys, drawing type with anchors, or call) and states that unmatched names are reported explicitly with a fallback recommendation. It does not say what happens on ambiguous or multiple matches, which keeps it off a 5.

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

Conciseness3/5

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

It is short and the purpose is front-loaded, but the first sentence is a dense run-on whose long enumeration largely duplicates the 'kind' enum and the return-type list from the schema. The lookup-mode instruction is correctly placed at the end where it is easy to find.

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 no output schema, the description takes on the job of describing returns and does so at a useful level of abstraction (target option, feature switch, style key, indicator id with defaults, drawing anchors, or call). It covers the no-match case as well; only ambiguity and result-set size when using query are left unaddressed.

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% and both enums are self-documenting, so the schema already carries the parameter burden and the baseline of 3 applies. The description only restates the name-versus-query split and adds no format, precedence, or interaction rules beyond what the schema declares.

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 first sentence names a specific verb (look up / map) and resource (a TradingView charting-library name) and enumerates the classes of names covered, so the tool's scope is unambiguous. It does not explicitly distinguish itself from siblings such as convert_widget_options, migration_plan, or get_indicator, so it stops short of a 5.

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?

The final clause gives operational guidance on the two lookup modes ('Look up one name with name, or search the table with query'), which is genuinely useful. However, there is no guidance on when to reach for this tool rather than the sibling conversion or listing tools, and no stated precedence when both name and query are supplied.

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