What Claude Can Read — MCP Tool Catalog

When you connect Claude to TTMT, it gets a set of tools — small, named actions it can call to fetch a slice of your trading data and answer a question in plain language. This page lists all of them so you know exactly what Claude can see when you ask it something.

Everything here is read-only

Every tool below only reads your data. Nothing on this page can place a trade, modify or close a position, change a setting, or move funds — and none of it can touch another user's data. There is no write tool, and no plans you make with Claude take effect until you apply them yourself in the dashboard. If Claude ever says it "placed" or "closed" a trade for you, that is a mistake — it cannot.

The 19 tools

Each tool answers a specific kind of question. You never call these by name — you just ask Claude a normal question, and it picks the right tool (or chains several) on its own. The example column shows the sort of thing that triggers each one.

Tool	What it does	Example question
list_accounts	Lists your connected MetaTrader accounts with id, label, currency, type, and current halt state.	"Which of my accounts are halted right now?"
list_trades	Lists trades with account, channel, status, symbol, and date filters. Paginated, newest first.	"Show me my losing XAUUSD trades this week."
get_trade	Pulls one trade by its trd_* reference or UUID — the signal, its positions and orders, and a reconstructed lifecycle timeline.	"Walk me through trade trd_abc123."
get_trade_trace	The deep dive: a compressed, redacted, step-by-step engine trace for one trade or signal (trd_* / sig_*), for when the timeline alone doesn't explain why something happened.	"Why did trd_abc123 only fill 2 of 4 layers?"
list_positions	Your currently open and partially closed positions, with a server-computed total unrealized P&L and a by-symbol breakdown.	"What's my total floating P&L right now?"
get_performance	Aggregated closed-trade performance — net P&L, win rate, profit factor, average realized R — optionally grouped by account, channel, profile, symbol, or month.	"How does my Aggressive profile compare to Balanced last month?"
get_settings	Resolves your effective settings across both layers (your base row plus any channel-bound profile override), naming which layer supplied each field.	"What settings apply when GoldFX signals hit my live account?"
get_profiles	Trading-profile summaries, or one profile fully resolved so you can see every value it actually uses.	"What does my Aggressive profile actually override?"
get_digest	A one-call activity rollup for a period: closed P&L, opened trades, open positions, halted accounts, skipped signals, and your best and worst channel.	"Give me my morning trading summary."
list_channels	Lists your tracked channels with their per-account routing assignments and bound profiles.	"Which channels route to my demo account?"
list_signals	Lists parsed signals — including the ones that were not traded (rejected, ignored, or skipped).	"Why didn't my last EURUSD signal get traded?"
get_risk_status	Per-account daily-loss-halt state plus the recent risk-limit audit trail.	"Show me the halt history on my live account this week."
settings_healthcheck	An advisory review that pairs your settings with your realized per-profile and per-channel performance and flags anything mechanically off. Never a backtest.	"Is my current config actually working well?"
preview_execution	Given a hypothetical signal and your current (or a named) settings, returns the exact adaptive order plan the platform would produce. Pure computation — no trade is placed.	"If I got a XAUUSD BUY signal now, what would my order plan look like?"
get_market_status	Whether the forex market is open right now and the next open/close time — DST-aware. Handy when nothing seems to be trading.	"Is the market open right now?"
get_drawdown	Realized equity-curve stats from your closed trades: maximum and current drawdown, longest win/loss streaks, and how long recovery took.	"What's my max drawdown, and how long did it take to recover?"
get_calendar_performance	Closed-trade performance bucketed by weekday, hour, or trading session (Sydney / Tokyo / London / New York), so you can see when you trade best.	"Am I a better trader in the London or the New York session?"
get_exposure	Your open positions broken down by currency — net long/short exposure per currency, per-symbol subtotals, and a warning when too much sits on one leg.	"How exposed am I to the US dollar right now?"
explain_skip	A one-call explanation of why one signal was or wasn't traded — its status, the channel's routing, any risk halts around that time, and the engine trace when available.	"Why exactly didn't my last EURUSD signal get traded?"

About preview_execution

preview_execution is the one tool that describes a trade that doesn't exist yet — it answers "what would happen?" It runs the same order-planning math the live engine uses, but it is pure calculation. Nothing is sent to your broker and no order is created. It is a preview, not a button.

Resources (5)

Alongside the tools, the connector exposes five resources — reference material Claude can pull in to ground its answers in TTMT's own terms rather than guessing.

Resource	What it holds
ttmt://glossary	Plain-language explanations of TTMT concepts — layered entries, take-profit redistribution, realized R, effective settings, halts, broadcast mode, soft delete.
ttmt://settings/schema	A field-by-field reference for your trading settings: the adaptive order engine, TP strategy, risk limits, breakeven, trailing stop, and the two-layer inheritance model.
ttmt://accounts	Your connected accounts with their current halt state — the same data as list_accounts, re-fetched fresh on every read.
ttmt://trades/{ref}	One trade by its trd_* reference or UUID — the same detail as get_trade, so your client can link straight to a single trade.
ttmt://channels/{name}	One tracked channel by name — its per-account routing assignments and bound profile.

These are read-only too. They give Claude the vocabulary and structure it needs to explain your numbers correctly.

Want a guided starting point?

You don't have to know which tool to reach for. The connector also ships seven ready-made prompts — one-click starting points like a morning review, a risk review, or a channel deep-dive — that chain the right tools together for you. See MCP Prompts for what each one does and how to run it.

Related pages

• MCP Prompts — the seven guided prompts and when to use each.
• MCP Security & Access — how read-only access is enforced, sign-in, and rate limits.