Skip to main content
Glama
Sign In
TradingView-MCP

TradingView-MCP

by tedorigawa001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

preflight_bookmap_flow_price_join

Verifies a local Bookmap Collector session's receipt-time-only join coverage against the active EURUSD M1/M5 chart, confirming proxy alignment without creating outcomes, chart changes, or orders.

Instructions

Read a local Bookmap Collector session and verify its conservative, receipt-time-only join coverage to the active EURUSD M1 or M5 chart. Bookmap CME flow is retained as a single-venue futures proxy, never presented as spot-FX-wide flow. This preflight creates no candidate, outcome study, chart change, or order.

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": {
      "expected_symbol": "<expected_symbol>",
      "expected_timeframe": "<expected_timeframe>"
    },
    "name": "preflight_bookmap_flow_price_join"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo
session_fileNoCollector JSONL basename. Default: latest lexicographic session in the configured local directory
expected_symbolYes
interval_secondsNo
minimum_intervalsNo
expected_timeframeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.10

TDQS

A4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool creates no candidate, outcome study, chart change, or order, and it qualifies Bookmap flow as a single-venue futures proxy rather than spot-FX-wide flow. It stops short of describing failure modes or file modification behavior, but the main safety-relevant traits are covered.

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

Conciseness5/5

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

The description is three focused sentences, each earning its place: purpose, data caveat, and safety guarantee. It is dense but not bloated, and the key constraints are front-loaded.

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?

The description explains purpose, data semantics, and non-mutation, but with no output schema it should also indicate what a successful verification returns or how mismatches are surfaced. Given the domain-specific jargon and six parameters, the description is not fully self-sufficient.

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

Parameters2/5

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

Schema description coverage is only 17%, and the description only implicitly covers expected_symbol/expected_timeframe via 'EURUSD M1 or M5' and session_file via 'local Bookmap Collector session'. It does not clarify count, interval_seconds, or minimum_intervals, which are important to this verification workflow.

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

Purpose5/5

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

The description uses specific verbs 'Read' and 'verify' against a precise resource: a local Bookmap Collector session joined to the active EURUSD M1/M5 chart. It also explicitly states it creates no candidate, outcome study, chart change, or order, which sharply differentiates it from the many research and study sibling tools.

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?

It is clear this is a preflight verification step to run before relying on Bookmap flow as a proxy for EURUSD chart context. It does not explicitly name alternative tools or spell out when-not-to-use conditions, but the read-only preflight framing and data qualification give sufficient guidance for selection.

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