Skip to main content
Glama

Plan a move from TradingView

migration_plan
Read-onlyIdempotent

How to move an app from TradingView's Advanced Charts / Trading Platform (the charting library) or from Lightweight Charts to TradeCanvas: the steps in order, what to search the app's code for and which tool maps what each search finds…

Instructions

How to move an app from TradingView's Advanced Charts / Trading Platform (the charting library) or from Lightweight Charts to TradeCanvas: the steps in order, what to search the app's code for and which tool maps what each search finds, and what to check at the end. Call it first.

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_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A4/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered and the description correctly spends its words elsewhere. It adds behavior the annotations cannot: the return is a plan (ordered steps, search strings, tool mapping, verification checklist), not an execution of the migration. With no output schema, that disclosure is the only source of return-shape information, which is exactly what is needed.

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?

A single front-loaded sentence that moves from scope to plan contents to the 'Call it first' directive, with no filler. It is dense but every clause carries information; a short bulleted breakdown would read slightly better, which keeps it off a 5.

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

Completeness5/5

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

There is no output schema, and the description compensates by stating what the plan contains, plus the ordering rule that determines correct invocation relative to the conversion and lookup tools. For a one-parameter read-only planning tool, nothing an agent needs in order to call it correctly is missing.

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%, so the single 'source' parameter and its two enum values are already fully documented, including the default. The description's restatement of the two library families is consistent with the enum but adds no syntax, default, or edge-case meaning beyond it, so the baseline of 3 applies.

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 names a concrete task and both supported origins ('move an app from TradingView's Advanced Charts / Trading Platform ... or from Lightweight Charts to TradeCanvas') and enumerates what the plan contains: ordered steps, code-search targets, the tool that maps each finding, and end-of-migration checks. That is far more specific than the title alone and makes the resource unambiguous, though it never names the sibling (migration_lookup) it is distinct from.

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?

'Call it first' gives an explicit ordering rule relative to every other tool in the set, which is real when-to-use guidance rather than an implication. It stops short of stating when not to use it (e.g., for a point lookup that migration_lookup may already answer), so it is clear context without exclusions.

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