LuxAlgo for AI agents: the Library, prop firms, Market Trackers, Edge Stats, and your Trade Journal
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
The catalog of session-statistics questions the hosted store precomputes nightly — gap fills, opening-range breakouts, day-of-week effects, event-day behavior, and more. Each preset states in plain language what its number means. Returns preset ids for edge_report.
Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
Narrow to one category (the result lists all categories)
The catalog of session-statistics questions the hosted store precomputes nightly — gap fills, opening-range breakouts, day-of-week effects, event-day behavior, and more. Each preset states in plain language what its number means. Returns preset ids for edge_report.
| Argument | Type | Description |
|---|---|---|
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
| category | string | Narrow to one category (the result lists all categories) |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"context"
],
"properties": {
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
},
"category": {
"type": "string",
"description": "Narrow to one category (the result lists all categories)"
}
}
}One precomputed session-statistics result: P(outcome | conditions) for a preset on a hosted symbol, in the engine's full honesty envelope — the estimate with N and a Wilson 95% confidence interval, minimum-sample guards, a first-half vs second-half stability split, per-year counts, the value distribution where the outcome is continuous, and the disclaimer. Historical conditional frequencies, not predictions. Preset ids come from edge_presets; symbols from edge_symbols.
| Argument | Type | Description |
|---|---|---|
| preset* | string | Preset id, e.g. 'gap-fill' — see edge_presets |
| symbol* | string | Hosted symbol, e.g. 'BTCUSDT' — see edge_symbols |
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"preset",
"symbol",
"context"
],
"properties": {
"preset": {
"type": "string",
"minLength": 1,
"description": "Preset id, e.g. 'gap-fill' — see edge_presets"
},
"symbol": {
"type": "string",
"minLength": 1,
"description": "Hosted symbol, e.g. 'BTCUSDT' — see edge_symbols"
},
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
}
}
}What the hosted Edge Stats store covers: the symbols, their session calendars, coverage windows, session counts, and when the nightly build last ran. Session statistics (how often a setup actually worked, with sample sizes and confidence intervals) come from the open-source edge-stats engine over free market data. Start here, then edge_presets for the questions you can ask, then edge_report for a result.
| Argument | Type | Description |
|---|---|---|
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"context"
],
"properties": {
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
}
}
}Log a trade by adding its fills to a `manual` or `import` journal account (never a broker-synced one — the sync owns those). The journal derives trades from fills: a long round trip is a buy fill then a sell fill, a short is sell then buy, scale-ins and partial exits are just more fills, and a lone fill opens a position. Times are ISO 8601 instants with offset; fees are per fill. Fills identical to existing ones are skipped as duplicates. Returns the insert counts and the trade(s) the fills now belong to, with `key`s for journal_update_trade. Correcting or removing an existing fill is done in the app, not here. Requires signing in with a LuxAlgo account (OAuth).
| Argument | Type | Description |
|---|---|---|
| fills* | array | The fills, in any order. |
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
| accountId* | string | A `manual` or `import` account id from journal_list_accounts. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"accountId",
"fills",
"context"
],
"properties": {
"fills": {
"type": "array",
"items": {
"type": "object",
"required": [
"symbol",
"side",
"quantity",
"price",
"executedAt"
],
"properties": {
"fee": {
"type": "number",
"minimum": 0,
"description": "Commission and fees for this fill, in the account currency. Default 0."
},
"side": {
"enum": [
"buy",
"sell"
],
"type": "string"
},
"price": {
"type": "number",
"minimum": 0,
"description": "Fill price per unit."
},
"symbol": {
"type": "string",
"maxLength": 30,
"minLength": 1,
"description": "Ticker as the user names it, e.g. 'AAPL', 'ES', 'BTCUSDT'."
},
"quantity": {
"type": "number",
"description": "Units, shares or contracts filled — always positive; `side` carries the direction.",
"exclusiveMinimum": 0
},
"assetClass": {
"enum": [
"equity",
"option",
"futures",
"forex",
"crypto",
"cfd",
"other"
],
"type": "string"
},
"executedAt": {
"type": "string",
"minLength": 1,
"description": "When the fill happened — ISO 8601 with a UTC offset, e.g. '2026-09-08T13:35:00-04:00'. Order among fills follows this."
}
}
},
"maxItems": 100,
"minItems": 1,
"description": "The fills, in any order."
},
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
},
"accountId": {
"type": "string",
"minLength": 1,
"description": "A `manual` or `import` account id from journal_list_accounts."
}
}
}Where the P&L actually comes from: closed trades in the window grouped nine ways — weekday, time of day, hold time, symbol, side, position size, tag, rating and asset class — each group with trade count, wins, losses, net P&L, average net P&L and win rate (breakevens excluded). Defaults to all time, since groups need sample size; narrow with `range` or `from`/`to`. The tool for 'what am I good or bad at' questions; journal_overview has the headline numbers. Requires signing in with a LuxAlgo account (OAuth).
| Argument | Type | Description |
|---|---|---|
| to | string | Inclusive end day (YYYY-MM-DD, journal timezone). Overrides `range`. |
| from | string | Inclusive start day (YYYY-MM-DD, journal timezone). Overrides `range`. |
| range | string | Named window ending today in the journal timezone. Ignored when from/to are given. |
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
| accounts |
One month of the P&L calendar: week rows of day cells (net and gross P&L, fees, trade/win/loss/breakeven counts, volume; null for days with no trades), each week's net P&L and trade count, and the month's net P&L, trade count, trading days and winning days. Days are in the journal timezone. Omit `month` for the current month. Drill into one day with journal_get_day. Requires signing in with a LuxAlgo account (OAuth).
| Argument | Type | Description |
|---|---|---|
| month | string | Month as YYYY-MM. Default: the current month in the journal timezone. |
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
| accounts | array | Journal account ids to scope to (from journal_list_accounts). Omit for every account, archived ones included. Unknown ids are rejected. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"context"
],
"properties": {
"month": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}$",
"description": "Month as YYYY-MM. Default: the current month in the journal timezone."
},
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
},
"accounts": {
"type": "array",
"items": {
"type": "string",
"minLength": 1
},
"maxItems": 50,
"minItems": 1,
"description": "Journal account ids to scope to (from journal_list_accounts). Omit for every account, archived ones included. Unknown ids are rejected."
}
}
}A single trading day: its stats (null when nothing traded), its trades (closed that day, or opened that day and still open) as summaries, and the day's notes with their ids. `date` is a YYYY-MM-DD day key in the journal timezone. Use it for 'how did Tuesday go', and to find note ids for journal_update_note. Requires signing in with a LuxAlgo account (OAuth).
| Argument | Type | Description |
|---|---|---|
| date* | string | The day, YYYY-MM-DD in the journal timezone. |
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
| accounts | array | Journal account ids to scope to (from journal_list_accounts). Omit for every account, archived ones included. Unknown ids are rejected. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"date",
"context"
],
"properties": {
"date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "The day, YYYY-MM-DD in the journal timezone."
},
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
},
"accounts": {
"type": "array",
"items": {
"type": "string",
"minLength": 1
},
"maxItems": 50,
"minItems": 1,
"description": "Journal account ids to scope to (from journal_list_accounts). Omit for every account, archived ones included. Unknown ids are rejected."
}
}
}One trade in full: the summary fields plus its fills (each with the effective values, what the source reported, the user's corrections and whether it is hidden), per-exit gross P&L, hidden fills inside the trade's span, and every annotation — notes, tags, mistakes, playbook id, stop loss, profit target, review time. Use after journal_list_trades or journal_get_day when the user asks about a specific trade or before annotating it. Requires signing in with a LuxAlgo account (OAuth).
| Argument | Type | Description |
|---|---|---|
| key* | string | The trade's `key` exactly as returned by journal_list_trades, journal_get_day, journal_search_notes or journal_add_trade. Never construct one. |
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"key",
"context"
],
"properties": {
"key": {
"type": "string",
"minLength": 1,
"description": "The trade's `key` exactly as returned by journal_list_trades, journal_get_day, journal_search_notes or journal_add_trade. Never construct one."
},
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
}
}
}The signed-in user's trade-journal accounts — id, name, broker, kind (`sync` mirrors a live broker connection, `import` came from statements, `manual` is hand-entered), currency, initial balance, P&L lot method, last broker sync, archived state — plus `timeZone`, the journal timezone every date in the journal tools is expressed in. Call this first: every other journal tool's `accounts` filter takes these ids and rejects unknown ones, and journal_add_trade needs a `manual` or `import` account. An empty list means no journal yet. Requires signing in with a LuxAlgo account (OAuth).
| Argument | Type | Description |
|---|---|---|
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"context"
],
"properties": {
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
}
}
}The user's annotation vocabulary: every tag, mistake and playbook id they have put on any trade (open or closed), most-used first with the number of trades carrying each. Check it before journal_update_trade so new annotations reuse the user's own words instead of minting near-duplicates. Per-trade tags are on each trade summary, not here. Requires signing in with a LuxAlgo account (OAuth).
| Argument | Type | Description |
|---|---|---|
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
| accounts | array | Journal account ids to scope to (from journal_list_accounts). Omit for every account, archived ones included. Unknown ids are rejected. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"context"
],
"properties": {
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
},
"accounts": {
"type": "array",
"items": {
"type": "string",
"minLength": 1
},
"maxItems": 50,
"minItems": 1,
"description": "Journal account ids to scope to (from journal_list_accounts). Omit for every account, archived ones included. Unknown ids are rejected."
}
}
}Trade summaries — `key`, account, symbol, asset class, direction, status (open/win/loss/breakeven), open and close times, quantity and open quantity, average entry/exit, gross and net P&L, fees, fill count, duration, realized R, tags, rating, reviewed flag, hasNotes — newest-opened first by default. `sort` orders by any of openedAt, closedAt, netPnl, grossPnl, durationMs, quantity, symbol or rating (names match the response fields); `order` is desc unless set, except symbol which defaults to asc. Trades lacking the sort value (open trades for closedAt/durationMs, unrated for rating) come last in either order; netPnl is after fees, grossPnl before. Filter by account ids, open-day window (`from`/`to` are inclusive YYYY-MM-DD day keys in the journal timezone, applied to the trade's open day; open positions are always listed), symbol, direction, status or one exact tag. Keyset-paginated: pass `nextCursor` back as `cursor` with the same sort, order and filters. Examples: biggest winners this month = from/to + sort netPnl; worst by gross = sort grossPnl, order asc, status loss; longest holds = sort durationMs. Summaries carry no fills or note text: journal_get_trade with the `key` has those. Requires signing in with a LuxAlgo account (OAuth).
| Argument | Type | Description |
|---|---|---|
| to | string | Inclusive end day (YYYY-MM-DD, journal timezone). Overrides `range`. |
| tag | string | Trades carrying exactly this tag (see journal_list_tags). |
| from | string | Inclusive start day (YYYY-MM-DD, journal timezone). Overrides `range`. |
| sort | string | Field to order by; default openedAt. Trades without a value for it come last in either order. |
The journal dashboard in one call for a window: performance metrics (net/gross P&L, fees, win rate, day win rate, profit factor, expectancy, average win/loss and their ratio, largest win/loss, streaks, max drawdown, recovery factor, profit concentration, average realized R), the Edge Score with its six components, per-day P&L stats, the cumulative equity curve, open positions, and the accounts and settings the numbers cover. Closed trades bucket by close day in the journal timezone; open positions count toward any window that reaches today. `compare: true` adds `previous` — the equal-length window just before. Defaults to the last 30 days; pass `range: 'all'` or explicit `from`/`to` for more. Null metrics are not computable yet (e.g. no losses → `profitFactorIsInfinite`). Use journal_breakdown for where the P&L comes from and journal_list_trades for the trades themselves. Requires signing in with a LuxAlgo account (OAuth).
| Argument | Type | Description |
|---|---|---|
| to | string | Inclusive end day (YYYY-MM-DD, journal timezone). Overrides `range`. |
| from | string | Inclusive start day (YYYY-MM-DD, journal timezone). Overrides `range`. |
| range | string | Named window ending today in the journal timezone. Ignored when from/to are given. |
| compare | boolean | Also compute the equal-length window immediately before this one. |
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
Search the notes feed — day notes and trades that carry notes — newest first as one stream split by kind: `notes` (day notes, with ids for journal_update_note) and `tradeNotes` (the trade summary with its note text; annotate via journal_update_trade). Filter by case-insensitive text (`q`), day-key window, symbol (trade notes only — day notes have no symbol and drop out) and account ids; keyset-paginated via `cursor`/`nextCursor`. Omit every filter for the latest notes. Requires signing in with a LuxAlgo account (OAuth).
| Argument | Type | Description |
|---|---|---|
| q | string | Substring to look for in note text, case-insensitive. |
| to | string | Inclusive end day (YYYY-MM-DD, journal timezone). Overrides `range`. |
| from | string | Inclusive start day (YYYY-MM-DD, journal timezone). Overrides `range`. |
| limit | integer | Page size, default 25. |
| cursor | string | `nextCursor` from the previous page; keep every other argument identical. |
| symbol | string | |
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
Replace a day note's text and/or move it to another day, by note id (from journal_get_day or journal_search_notes). The body is replaced whole — to append, read the current text first and send the full new version. Trade notes are edited with journal_update_trade, not here. Returns the updated note. Day notes in the LuxAlgo journal: https://docs.luxalgo.com/platform/workspaces/journal/notes Requires signing in with a LuxAlgo account (OAuth).
| Argument | Type | Description |
|---|---|---|
| body | string | The full new text. |
| date | string | Move the note to this day, YYYY-MM-DD in the journal timezone. |
| noteId* | string | The note's `id`. |
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"noteId",
"context"
],
"properties": {
"body": {
"type": "string",
"maxLength": 50000,
"minLength": 1,
"description": "The full new text."
},
"date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Move the note to this day, YYYY-MM-DD in the journal timezone."
},
"noteId": {
"type": "string",
"minLength": 1,
"description": "The note's `id`."
},
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
}
}
}Annotate a trade — the user-owned fields only: `notes` (free text about this trade), `tags`, `mistakes`, `playbookId`, `rating` 1–5, `stopLoss` and `profitTarget` (price levels; the stop is what realized R is measured against) and `reviewed`. `tags`/`mistakes` replace the whole list; use `addTags`/`removeTags`/`addMistakes`/`removeMistakes` to change a few entries without clobbering the rest (check journal_list_tags for the user's existing words). Pass null to clear a field. Does not touch fills, prices or P&L — those derive from the fills. Returns the updated trade in full. Requires signing in with a LuxAlgo account (OAuth).
| Argument | Type | Description |
|---|---|---|
| key* | string | The trade's `key` exactly as returned by journal_list_trades, journal_get_day, journal_search_notes or journal_add_trade. Never construct one. |
| tags | any | |
| notes | any | Replaces the trade's note text; null clears it. |
| rating | any | Execution quality 1–5; null clears it. |
| addTags | array | Tags to add (existing ones are kept; case-insensitive duplicates are ignored). |
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
Add a new note to a trading day — any day, traded or not; `date` is YYYY-MM-DD in the journal timezone. Days hold any number of notes, so this never overwrites: to change an existing note use journal_update_note, and for a note about one specific trade use journal_update_trade's `notes`. Returns the note with its id. Day notes in the LuxAlgo journal: https://docs.luxalgo.com/platform/workspaces/journal/notes Requires signing in with a LuxAlgo account (OAuth).
| Argument | Type | Description |
|---|---|---|
| body* | string | The note text (plain text or markdown). |
| date* | string | The day the note belongs to, YYYY-MM-DD in the journal timezone. |
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"date",
"body",
"context"
],
"properties": {
"body": {
"type": "string",
"maxLength": 50000,
"minLength": 1,
"description": "The note text (plain text or markdown)."
},
"date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "The day the note belongs to, YYYY-MM-DD in the journal timezone."
},
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
}
}
}Explain a trading concept: the Library's full write-up as markdown — definition, formula, how traders read it, and its indicator implementations. Use for any 'what is X / how does X work' question. Needs the exact slug — find it with library_search or library_list_concepts.
| Argument | Type | Description |
|---|---|---|
| slug* | string | Exact concept slug, e.g. 'rsi' or 'order-blocks' — from search or list results |
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"slug",
"context"
],
"properties": {
"slug": {
"type": "string",
"minLength": 1,
"description": "Exact concept slug, e.g. 'rsi' or 'order-blocks' — from search or list results"
},
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
}
}
}A family's hub page as markdown — the written overview of that school of analysis plus its complete concept roster. Use after library_list_families, or when the user asks about a whole area like 'SMC' or 'Wyckoff'.
| Argument | Type | Description |
|---|---|---|
| key* | string | Family key, e.g. 'smc-ict' |
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"key",
"context"
],
"properties": {
"key": {
"enum": [
"trend",
"momentum",
"volatility",
"volume-orderflow",
"market-structure",
"smc-ict",
"wyckoff",
"elliott-harmonics",
"patterns",
"levels",
"statistics",
"machine-learning",
"time-seasonality",
"sentiment-breadth",
"risk-exits",
"meta-composition",
"validation"
],
"type": "string",
"description": "Family key, e.g. 'smc-ict'"
},
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
}
}
}Details for one indicator: what it does, how to read it, family, concept links, preview image — plus whether its source code is available (fetch the code itself with library_get_source_code). Use when the user asks about a specific indicator.
| Argument | Type | Description |
|---|---|---|
| slug* | string | Indicator slug, e.g. 'tri-star' |
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"slug",
"context"
],
"properties": {
"slug": {
"type": "string",
"minLength": 1,
"description": "Indicator slug, e.g. 'tri-star'"
},
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
}
}
}The full, working source code of a Library indicator (works on TradingView). Kept separate from library_get_indicator because sources are long — call it only when the user wants the code itself.
| Argument | Type | Description |
|---|---|---|
| slug* | string | Indicator slug |
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"slug",
"context"
],
"properties": {
"slug": {
"type": "string",
"minLength": 1,
"description": "Indicator slug"
},
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
}
}
}Browse every trading and technical-analysis concept in the Library — paginated, optionally one family. Use to enumerate a topic area or find slugs for library_get_concept; for keyword lookup prefer library_search.
| Argument | Type | Description |
|---|---|---|
| page | integer | Default 0 |
| family | string | |
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
| page_size | integer | Default 50 |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"context"
],
"properties": {
"page": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0,
"description": "Default 0"
},
"family": {
"enum": [
"trend",
"momentum",
"volatility",
"volume-orderflow",
"market-structure",
"smc-ict",
"wyckoff",
"elliott-harmonics",
"patterns",
"levels",
"statistics",
"machine-learning",
"time-seasonality",
"sentiment-breadth",
"risk-exits",
"meta-composition",
"validation"
],
"type": "string"
},
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
},
"page_size": {
"type": "integer",
"maximum": 200,
"minimum": 1,
"description": "Default 50"
}
}
}The Library's top-level taxonomy: 17 families of trading concepts (trend, momentum, SMC/ICT, statistics, …) with concept counts and hub links. The natural first call for orientation.
| Argument | Type | Description |
|---|---|---|
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"context"
],
"properties": {
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
}
}
}Browse the indicator catalog with filters and server-side sorting (newest first by default). Filter by family, concept slug (implementations of one concept), tags (ids from library_list_tags, AND-combined), trading platform, or plan tier. Use for structured browsing — 'latest indicators', 'everything in the volatility family', 'indicators implementing liquidity sweeps'; for keyword discovery prefer library_search.
| Argument | Type | Description |
|---|---|---|
| page | integer | Default 0 |
| sort | string | Default: date |
| tags | array | Tag ids (from library_list_tags); an indicator must carry every tag |
| text | string | Server-side text filter |
| tier | string | Only indicators included in this LuxAlgo plan tier |
| family | string | |
| concept | string | Concept slug — only indicators linked to this concept, e.g. 'rsi' |
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
The Library's indicator tag vocabulary (behavioral traits like 'Volatility', 'Trailing-Stop', 'Repainting Functionality'). Returns ids to pass as the tags filter of library_list_indicators — tags are orthogonal to the concept-family taxonomy.
| Argument | Type | Description |
|---|---|---|
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"context"
],
"properties": {
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
}
}
}Search the LuxAlgo Library — the encyclopedia of trading and technical analysis. One query over 800+ concepts (alias-aware: 'stochastics' finds Stochastic Oscillator) and 800+ ready-to-use indicators. Start here whenever you have a name, informal term, or topic; results carry slugs for the get tools plus canonical URLs for citation.
| Argument | Type | Description |
|---|---|---|
| type | string | Limit to 'concepts' (explanations) or 'indicators' (implementations); default all |
| limit | integer | Max results (default 10) |
| query* | string | A concept, indicator name, alias, or topic — e.g. 'order blocks', 'mean reversion', 'stochastics' |
| family | string | Narrow to one concept family |
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
The signed-in user's LuxAlgo account: plan tier, entitlements (limits such as alerts, historical bars, AI credits) and profile basics. Use it to tailor answers to what the user's plan actually allows, or when the user asks what plan they are on. Requires signing in with a LuxAlgo account (OAuth).
| Argument | Type | Description |
|---|---|---|
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"context"
],
"properties": {
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
}
}
}Fetch one directory challenge's complete ruleset (ChallengeSpec), adapted from the live LuxAlgo directory: evaluation steps (profit targets in percent units of the initial account, minimum trading days, time limits); the daily-loss rule with its exact semantics (basis = measured from prior-day balance vs prior-day equity; limitBasis = whether a pct limit is a fixed allowance of the initial balance or recomputed daily from the anchor; evaluation = breached on an intraday touch vs only at the close; includesOpenPnl = whether floating P&L can breach it); the max-loss rule and its drawdown mode (How the max-loss floor behaves - the single most consequential rule difference between firms. 'static-initial': floor fixed at initial balance minus the limit; never moves (classic CFD two-step). 'trailing-realized-eod': floor ratchets up with end-of-day balance highs; intraday highs do not move it. 'trailing-intraday-unrealized': floor trails the peak unrealized equity intraday and never stops trailing (futures-style; the most-miscalculated rule in the industry: it cuts pass probability dramatically). 'trailing-locks-at-initial': trails intraday peak equity until the floor reaches the initial balance, then freezes (common futures variant). Locking is also composable: locksAtInitial adds the same lock to an EOD trail, and lockOffsetAmount shifts the lock level to initial balance + that amount (e.g. 100 models 'stops trailing $100 above the start').); per-step consistency rules (steps[].consistency.maxBestDayProfitPct - SIMULATED: one outsized day effectively raises the target until the best-day share complies); fees (price, one-time vs monthly billing, reset fee, activation fee, refundable-on-pass); funded terms (profit split percent, payout frequency, first-payout minimum days, and funded.payoutRules - SIMULATED payout gating: minWinningDays, winningDayMinProfit, per-payout caps maxPayoutPctOfProfit/maxPayoutAmount, bufferAmount, and a windowed consistencyMaxBestDayPct gate); flagsNotSimulated (rules the entry declares but the engine does not simulate - material caveats to relay to the user); and sources (the firm-page citation when the directory serves one). The result also carries `provenance` and `inferredFields` - every rule read from free text instead of a structured column is named there; relay them and treat the firm's page as authoritative. The returned `challenge` object is exactly the shape the simulation tools accept as inline `spec`: copy it, change a rule, and re-simulate to quantify how a rule variation moves pass probability and EV. UNITS: every *Pct rule field and every percent-mode risk value is in PERCENT UNITS (5 = 5%, 0.5 = 0.5%). The one exception is winRate, which is a FRACTION in [0, 1] (0.55 = 55% winners). Probabilities in results are fractions in [0, 1]. DATA SOURCE & PROVENANCE: firm data comes live from LuxAlgo's public, keyless prop-firm directory API - the data behind luxalgo.com/prop-firms. Rule semantics are used verbatim where the directory serves structured rule columns; where it serves only free text, semantics are inferred ONLY when one reasonable reading exists, and every inferred field is disclosed in `inferredFields` (provenance 'directory+inferred') - relay those to the user next to any numbers. Challenges whose loss rules cannot be established are refused as not simulatable rather than guessed. Firms change rules; each firm's own page is always authoritative. NOTE: this returns the simulatable encoding of one challenge's rules; the directory listing with every captured field, plus live offers, is propfirms_get and propfirms_search_challenges.
Simulate the SAME trader across several challenges (directory references and/or inline specs, up to 12) under identical options and seed, and return one row per challenge sorted by expected value. THIS IS NOT A RANKING: rows are ordered by EV for the caller's specific inputs - trader stats, risk sizing, and options - and a different trader profile reorders them. The tool computes data for the user's own decision; it implies no endorsement, league table, or recommendation of any firm, and results should be presented that way ('best EV for these inputs', never 'best firm'). Each row carries perAttemptPassProbability, fundedProbability, expectedAttempts, expectedCost, evTotal, pEvPositive, daysToFundedP50, and the challenge's flagsNotSimulated - challenges with more unsimulated rules have optimistic numbers, so compare flags alongside EV, not EV alone. Consistency rules and funded payout gating ARE simulated (engine v1), so EV already reflects them where a ruleset has them. For full per-challenge distributions run propfirms_simulate on the interesting rows. UNITS: every *Pct rule field and every percent-mode risk value is in PERCENT UNITS (5 = 5%, 0.5 = 0.5%). The one exception is winRate, which is a FRACTION in [0, 1] (0.55 = 55% winners). Probabilities in results are fractions in [0, 1]. DETERMINISM: identical inputs including `seed` reproduce byte-identical results on any platform. Include the seed and path count when reporting numbers so users can reproduce them exactly; re-run with a few different seeds to gauge Monte Carlo spread. ASSUMPTIONS: every result carries assumptions.flags - dataset-declared rules the engine does NOT simulate (e.g. scaling plans or soft daily lockouts, which make real odds worse than simulated) plus engine simplifications - and assumptions.disclaimer. These are material: always surface the flags and the disclaimer to the user alongside the numbers, never just the headline probability. Results are distributions under stated assumptions, not promises.
| Argument | Type | Description |
|---|---|---|
| seed | any | RNG seed (integer or string). Default 42. Same inputs + seed reproduce byte-identical results - include the seed when reporting so users can reproduce the numbers. |
One prop firm's full dossier by slug: general profile (platforms, markets, payments, Trustpilot, restricted countries), every challenge with its rules, live offers with promo codes and affiliate links, and the written overview (about, rules, payout policy, FAQ). Find slugs with propfirms_search. Uncaptured (null) fields are omitted; challenges reference applicable offers via offerIds into the firm-level offers list. For simulated pass odds on this firm's challenges (reference archetypes, same engine as luxalgo.com/prop-firms), use propfirms_pass_rates.
| Argument | Type | Description |
|---|---|---|
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
| propfirmId* | string | Public firm slug, e.g. 'ftmo' |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"propfirmId",
"context"
],
"properties": {
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
},
"propfirmId": {
"type": "string",
"minLength": 1,
"description": "Public firm slug, e.g. 'ftmo'"
}
}
}List the prop firms in the live LuxAlgo directory together with every simulatable challenge (challengeId, display name, account size, currency, price, and its rule-semantics provenance). Call this first to discover the firmId + challengeId pairs accepted by propfirms_challenge_rules, propfirms_simulate, propfirms_optimal_risk, propfirms_compare and propfirms_simulate_trades. Challenges whose loss-rule semantics cannot be established are listed under notSimulatable instead of being guessed. The listing is data, not endorsement: firms are alphabetical - no recommendation or ranking is implied, and none should be presented. DATA SOURCE & PROVENANCE: firm data comes live from LuxAlgo's public, keyless prop-firm directory API - the data behind luxalgo.com/prop-firms. Rule semantics are used verbatim where the directory serves structured rule columns; where it serves only free text, semantics are inferred ONLY when one reasonable reading exists, and every inferred field is disclosed in `inferredFields` (provenance 'directory+inferred') - relay those to the user next to any numbers. Challenges whose loss rules cannot be established are refused as not simulatable rather than guessed. Firms change rules; each firm's own page is always authoritative. NOTE: this lists only the firms and challenges whose rules the engine can encode honestly. The full directory — every visible firm with platforms, prices, payout terms, and live offers/promo codes — is served by propfirms_search, propfirms_search_challenges, and propfirms_search_offers.
| Argument | Type | Description |
|---|---|---|
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
Sweep risk-per-trade over a grid, run the full journey simulation at every point, and report two optima separately: bestByPassProbability (the risk that maximizes a single attempt's chance of passing) and bestByEv (the risk that maximizes expected value across attempts, fees and funded payouts). They usually differ (diverges=true) - and that divergence is the insight: lower risk survives loss limits more often, but EV also weighs the cost of extra attempts and the size of funded payouts, which can favor a different risk. Never present one number as THE optimal risk; report both optima and the trade-off, and let the user choose. The sweep uses common random numbers (the same seed at every grid point), so curves are smooth and the argmax is signal, not Monte Carlo noise. Grid units follow riskMode: percent units for percent modes (default grid 0.1 to 3 in steps of 0.1, i.e. 0.1%-3% per trade), currency per trade for 'fixed-amount' (set min/max/step explicitly). Parametric trader only (riskValue is not a parameter here - the grid supplies it). Cost scales with grid size: one full simulation per point, so ~30 points at the default 10,000 paths takes roughly 10 seconds; use fewer paths or a coarser grid for a first pass, then refine around the optima. UNITS: every *Pct rule field and every percent-mode risk value is in PERCENT UNITS (5 = 5%, 0.5 = 0.5%). The one exception is winRate, which is a FRACTION in [0, 1] (0.55 = 55% winners). Probabilities in results are fractions in [0, 1]. DETERMINISM: identical inputs including `seed` reproduce byte-identical results on any platform. Include the seed and path count when reporting numbers so users can reproduce them exactly; re-run with a few different seeds to gauge Monte Carlo spread. ASSUMPTIONS: every result carries assumptions.flags - dataset-declared rules the engine does NOT simulate (e.g. scaling plans or soft daily lockouts, which make real odds worse than simulated) plus engine simplifications - and assumptions.disclaimer. These are material: always surface the flags and the disclaimer to the user alongside the numbers, never just the headline probability. Results are distributions under stated assumptions, not promises. Results describe simulated outcomes of the user's own inputs under stated assumptions; they are not financial advice or a recommendation of any risk level.
| Argument |
|---|
Reference challenge pass rates computed live from the directory's encoded rules with the same engine, seed (42), path count (10,000) and reference archetypes luxalgo.com/prop-firms uses — per challenge and per archetype (developing 45% win rate / consistent 48% / proven edge 52%, all risking conservatively). Returns per-attempt pass probability with 95% CI, P(funded), expected attempts and total cost, EV, payout probability, funded-blowup probability, each cell's assumption flag ids, and the ruleset's provenance (structured directory columns vs fields inferred from listing text — always relay inferred fields). Deterministic per ruleset and cached — cheap to call. These are REFERENCE odds for orientation and comparison, not the user's personal odds: for their own statistics use propfirms_simulate (summary stats) or propfirms_simulate_trades (their real trade series). Not a ranking; a firm's page is authoritative for current rules (check lastVerified). Expected costs use the directory's listed challenge prices; full firm profiles and live offers are directory data (propfirms_get, propfirms_search_offers).
| Argument | Type | Description |
|---|---|---|
| firmId* | string | Directory firm id (propfirmId, e.g. 'ftmo') or firm name — from propfirms_list_simulatable. |
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
Search LuxAlgo's prop-firm catalog (proprietary trading firms offering funded accounts). Combine firm filters (platforms, markets, payment/payout methods, country availability, Trustpilot, year founded) with nested challenge filters (account size, price, steps, profit split, trading rules) and offer filters — a firm matches when at least one of its challenges/offers matches all of them. Omit every filter to list all firms. Use include to nest the matching challenges, live offers, and the written overview; for one firm's full dossier prefer propfirms_get. Uncaptured (null) fields are omitted from results; nested challenges reference offers via offerIds into the firm-level offers list. This tool returns directory data (what exists and on what terms), not outcomes: for simulated pass odds on a challenge found here, use propfirms_pass_rates or propfirms_simulate with its firm and challenge ids.
| Argument | Type | Description |
|---|---|---|
| sort | string | Sort key (default name) |
| text | string | Case-insensitive search over firm name and slug, e.g. 'ftmo' |
| steps | integer | Exact evaluation step count (1 = instant/funded, 2 = two-step, …) |
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
Search funded-account challenges across all visible prop firms. Filter by challenge rules (account size, fee, steps, profit split, drawdown mode, news/copy/auto trading, weekend holding, …) and by parent-firm properties. Pass propfirmId to list one firm's challenges, or challengeId to fetch specific ones. include=['offers'] returns a deduplicated top-level offers list, with each challenge referencing its applicable offers via offerIds (firm-wide offers included). Uncaptured (null) rule fields are omitted from results and never match filters. This returns each challenge's listed rules and terms, not outcomes: to simulate a challenge found here pass its ids to propfirms_simulate or propfirms_pass_rates, and to screen one strategy across many challenges at once use propfirms_validate_strategy.
| Argument | Type | Description |
|---|---|---|
| sort | string | Sort key (default accountSize descending) |
| text | string | Case-insensitive search over challenge name and firm name/slug |
| steps | integer | Exact evaluation step count (1 = instant/funded, 2 = two-step, …) |
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
Search promotional offers (discounts and promo codes) across prop firms — defaults to live (active, unexpired) offers only. propfirmId narrows to one firm; challengeId resolves the offers that apply to a challenge (firm-wide offers included). Every offer carries the promo code, discount, end date, and affiliate link.
| Argument | Type | Description |
|---|---|---|
| sort | string | Sort key (default: featured first, then discount) |
| text | string | Case-insensitive search over promo code, descriptions, and firm name/slug |
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
| offerId | array | Public offer ids |
| isActive | boolean | Defaults to live offers only; pass false to look at inactive offers |
| direction |
Monte Carlo-simulate a trader with the given statistics through a prop-firm challenge and (by default) a funded horizon. Answers: "What is my chance of passing per attempt, and of ever getting funded? How many attempts and how much total money should I expect? Is this challenge positive expected value for me, and which rule actually kills my attempts?" Identify the challenge EITHER by directory reference (firmId + challengeId, discovered via propfirms_list_simulatable; firmId accepts the directory id or the firm's name) OR by a full inline `spec` object - the exact shape propfirms_challenge_rules returns, so you can fetch a directory entry, change one rule, and re-simulate to model rule variations. Provide exactly one of the two forms; providing both or neither is an error. Directory references need network access; inline specs are fully offline. The trader is described by flattened parametric fields (one clean design used across all tools): winRate (a FRACTION 0-1), avgWinR/avgLossR and optional winStdR/lossStdR in R-multiples (sizes relative to the amount risked per trade), tradesPerDay with a 'fixed' or 'poisson' day model, and risk sizing via riskMode + riskValue (percent units for percent modes). If you have the user's raw trade series rather than summary stats, prefer propfirms_simulate_trades - it preserves streaks. Returns structuredContent with the full SimResult: perAttempt.passProbability with a Wilson 95% CI and per-step pass rates plus a failure breakdown by rule (daily-loss vs max-loss vs time-limit - which tells the user WHAT to fix); journey.fundedProbability, attempts and cost distributions (cost includes prices, resets, monthly billing, activation, minus refunds), costGivenFunded and daysToFunded; perAttempt.avgDaysWhenPassed/avgDaysWhenFailed and perAttempt.stagnationDays (the longest run of days without a new equity high per attempt - the dead time between progress, which grows sharply as risk per trade shrinks); funded-stage payout distributions plus funded.payoutProbability (P(at least one payout | funded)) and funded.daysToFirstPayout - with payout gating these can be the deciding numbers, since getting funded is not the same as getting paid; ev.evTotal (mean payouts minus costs) with evStandardError and pPositive; drawdown stats; and assumptions (the fully-resolved spec/profile/options the engine actually ran, plus flags and disclaimer). Histogram arrays are omitted unless includeHistograms=true. A compact human summary is returned as text alongside. SIMULATED RULES (engine v1): consistency rules (steps[].consistency) and funded payout gating (funded.payoutRules) are actually SIMULATED, not merely flagged. Consistency uses a rational stop rule (the trader stops a day once more profit cannot help and keeps trading until the best-day share complies - flag 'consistency-stop-rule'); payouts follow a maximum-withdrawal model (withdraw everything the rules allow above buffer/caps, never below the loss floor; balances and floors carry across payouts - flag 'funded-withdrawal-model'); a funded consistency gate is checked per payout window (flag 'funded-consistency-window-approximated'). UNITS: every *Pct rule field and every percent-mode risk value is in PERCENT UNITS (5 = 5%, 0.5 = 0.5%). The one exception is winRate, which is a FRACTION in [0, 1] (0.55 = 55% winners). Probabilities in results are fractions in [0, 1]. DETERMINISM: identical inputs including `seed` reproduce byte-identical results on any platform. Include the seed and path count when reporting numbers so users can reproduce them exactly; re-run with a few different seeds to gauge Monte Carlo spread. ASSUMPTIONS: every result carries assumptions.flags - dataset-declared rules the engine does NOT simulate (e.g. scaling plans or soft daily lockouts, which make real odds worse than simulated) plus engine simplifications - and assumptions.disclaimer. These are material: always surface the flags and the disclaimer to the user alongside the numbers, never just the headline probability. Results are distributions under stated assumptions, not promises. DATA SOURCE & PROVENANCE: firm data comes live from LuxAlgo's public, keyless prop-firm directory API - the data behind luxalgo.com/prop-firms. Rule semantics are used verbatim where the directory serves structured rule columns; where it serves only free text, semantics are inferred ONLY when one reasonable reading exists, and every inferred field is disclosed in `inferredFields` (provenance 'directory+inferred') - relay those to the user next to any numbers. Challenges whose loss rules cannot be established are refused as not simulatable rather than guessed. Firms change rules; each firm's own page is always authoritative.
Simulate a challenge by resampling the trader's OWN R-multiple trade series with a stationary block bootstrap instead of a win-rate model. Why resampling matters: challenge rules are breached by streaks, not by averages - a daily-loss limit dies to a cluster of losses inside one day, and a trailing drawdown dies to a losing streak right after an equity peak. Real trade series are streaky (autocorrelation, volatility clustering, edge that comes and goes), and the stationary bootstrap resamples contiguous blocks of the actual series (geometric length, mean blockMeanLength, default 5 trades), so the trader's real streak structure survives into every simulated day. A parametric model with identical summary statistics shuffles trades independently and therefore understates breach risk for streaky traders. Use propfirms_simulate when only summary stats are available; use this whenever the actual trades are. Provide the series as rSeries (array of R-multiples: each trade's P&L divided by the amount risked on it), rSeriesText (pasted JSON/CSV/whitespace text, optional 'R' suffix per value), or one of the timestamped-log inputs below; exactly one of the four, at least 10 trades, 100+ strongly recommended. Returns the same full SimResult as propfirms_simulate (structuredContent, histograms off by default) plus a text summary that also reports the sample's win rate and mean R. TIMESTAMPED LOGS: tradeLogText accepts a pasted CSV/TSV trade log with a header row (open time and R required; close time and direction optional; loose header names are matched; timestamps without an offset are read as UTC). The R-series and, unless tradesPerDay is passed, the trades-per-day rate are derived from the log, and parse warnings are surfaced in the text output. NEWS WINDOWS: with a timestamped input, newsFilter runs the simulation TWICE on the same seed and options, once on the full history and once without the trades opened inside configurable windows around scheduled releases (a built-in recurring-template calendar of high- and medium-impact events across USD, EUR, GBP, JPY, AUD, CAD, CHF, NZD, plus optional custom event times). The returned SimResult is the news-avoided scenario; structuredContent.newsComparison carries both scenarios' pass probability, funded probability and EV, the excluded-trade count, and a calendar caveat that must be relayed verbatim. PORTFOLIO MODE: tradeLogTexts (2 to 5 logs) merges several timestamped histories into one chronological series and simulates the combined account, so cross-strategy loss clustering survives. Overlap across the histories is ALWAYS analyzed and attached as structuredContent.portfolioOverlap; the text summary carries the audit-risk verdict, and a 'high' verdict is an explicit warning that a prop firm may audit or refuse payouts for correlated accounts. SIMULATED RULES (engine v1): consistency rules (steps[].consistency) and funded payout gating (funded.payoutRules) are actually SIMULATED, not merely flagged. Consistency uses a rational stop rule (the trader stops a day once more profit cannot help and keeps trading until the best-day share complies - flag 'consistency-stop-rule'); payouts follow a maximum-withdrawal model (withdraw everything the rules allow above buffer/caps, never below the loss floor; balances and floors carry across payouts - flag 'funded-withdrawal-model'); a funded consistency gate is checked per payout window (flag 'funded-consistency-window-approximated'). UNITS: every *Pct rule field and every percent-mode risk value is in PERCENT UNITS (5 = 5%, 0.5 = 0.5%). The one exception is winRate, which is a FRACTION in [0, 1] (0.55 = 55% winners). Probabilities in results are fractions in [0, 1]. DETERMINISM: identical inputs including `seed` reproduce byte-identical results on any platform. Include the seed and path count when reporting numbers so users can reproduce them exactly; re-run with a few different seeds to gauge Monte Carlo spread. ASSUMPTIONS: every result carries assumptions.flags - dataset-declared rules the engine does NOT simulate (e.g. scaling plans or soft daily lockouts, which make real odds worse than simulated) plus engine simplifications - and assumptions.disclaimer. These are material: always surface the flags and the disclaimer to the user alongside the numbers, never just the headline probability. Results are distributions under stated assumptions, not promises.
Answer 'which challenges would MY strategy actually pass?' in one call: simulate the given strategy through every simulatable challenge in the live directory (optionally scoped by productType, account-size range, priceMax, or firm) and split the results by an explicit, caller-stated bar. Describe the strategy EITHER as real trades (rSeries/rSeriesText R-multiples, preferred: the stationary block bootstrap preserves streaks, which is what breaches loss limits) OR as summary stats (winRate + avgWinR, optional spreads), plus tradesPerDay and risk sizing (riskMode + riskValue). The bar is minPassPerAttempt (a fraction, default 0.5) with optional requirePositiveEv; always state the bar when relaying results. Returns per challenge: pass probability per attempt with 95% CI, P(funded), expected attempts and total cost, EV over the funded horizon, P(EV>0), assumption flag ids, and which rule semantics were inferred from listing text. HONESTY FRAME: this is a screen of distributions for the caller's inputs and bar, NOT a ranking or endorsement; challenges whose rules cannot be encoded honestly are excluded and counted, never guessed; flagged (unsimulated) rules make numbers optimistic, so relay flags. One full simulation runs per challenge (default 5,000 paths each; results are deterministic per seed), and scopes above 40 challenges are refused rather than silently truncated: narrow the scope instead. Numbers move with risk sizing; sweep one challenge with propfirms_optimal_risk afterwards. Fees and expected costs use the directory's listed prices (live discounts are NOT applied); prices, firm profiles, and current offers are directory data (propfirms_search_challenges, propfirms_get, propfirms_search_offers).
| Argument | Type | Description |
|---|---|---|
| firm | string | Restrict to one firm by propfirmId or name (e.g. 'ftmo'). |
| seed | any | RNG seed (integer or string). Default 42. Same inputs + seed reproduce byte-identical results — include the seed when reporting so users can reproduce the numbers. |
The Market Trackers catalog: every dataset of US public-record market data the LuxAlgo pipeline publishes as CC0 dumps — congressional trades, insider (Forms 3/4/5) transactions, 13F holdings, federal contracts and grants, lobbying filings, FINRA short-sale volume, granted patents, clinical trials, FDA drug events, CFTC positioning, federal bills, FEC campaign finance, hearing transcripts, Federal Reserve communications, committee assignments, Wikipedia pageviews. Returns each dataset's row count, freshness, the years with data (live tree vs deep-history archives), and whether it is ticker-searchable. Pass dataset for the full field roster, filterable paths, caveats, per-year coverage, source health, and dump URLs — read it before composing trackers_query filters.
| Argument | Type | Description |
|---|---|---|
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
| dataset | string | One dataset for the detailed view; omit to list all |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"context"
],
"properties": {
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
},
"dataset": {
"enum": [
"congress-trades",
"insider-transactions",
"thirteenf-holdings",
"gov-contracts",
"gov-grants",
"lobbying-filings",
"short-volume",
"committee-assignments",
"patents",
"clinical-trials",
"fda-approvals",
"cot-reports",
"wiki-pageviews",
"bills",
"fec-candidates",
"fec-contributions",
"congress-hearings",
"fed-communications"
],
"type": "string",
"description": "One dataset for the detailed view; omit to list all"
}
}
}What the last daily publish added to one dataset — the newest ingestion day's rows (the dumps' latest.json), optionally narrowed by ticker or text. The cheapest way to see what is new: today's insider filings, this week's congressional disclosures, the latest lobbying registrations. Not available for snapshot-only bulk datasets (patents); use trackers_query there.
| Argument | Type | Description |
|---|---|---|
| sort | string | Order by event date (default newest) |
| text | string | Case-insensitive substring over the dataset's name/title fields (member, insider, issuer, recipient, registrant and client, sponsor, assignee, bill title, …); see textPaths in trackers_datasets |
| limit | integer | Rows to return (default 25, max 100) |
| where | object | Exact field matches by dot path, e.g. {"side":"buy"}, {"member.state":"CA"}, {"code":"P"}, {"formType":"4"}; string comparisons are case-insensitive, arrays match when any element does |
| offset | integer | Rows to skip, for paging (default 0) |
| ticker | string | Trading symbol, case-insensitive (e.g. 'NVDA'); matches the dataset's ticker field(s). Only datasets flagged tickerSearchable carry tickers. |
| context* |
Search one Market Trackers dataset by ticker, free text, exact field values, and event-date range, with paging and newest/oldest ordering. Data is read from year-sharded CC0 dumps: pass years (or since/until) to choose which years to read — default is the newest year with data. Deep-history years (see archiveYears in trackers_datasets) can be tens of MB compressed each, so read them one or two at a time; the tool refuses selections over its byte budget and says how to narrow. Every row carries provenance.sourceUrl (the SEC filing, disclosure, award, or record it came from). Examples: insider purchases at NVDA in 2024 → dataset insider-transactions, ticker NVDA, years [2024], where {code: 'P'}; a member of Congress's trades → congress-trades, text set to their name; who lobbied on a bill → lobbying-filings, text 'H.R.1234'.
| Argument | Type | Description |
|---|---|---|
| sort | string | Order by event date (default newest) |
| text | string | Case-insensitive substring over the dataset's name/title fields (member, insider, issuer, recipient, registrant and client, sponsor, assignee, bill title, …); see textPaths in trackers_datasets |
| limit | integer | Rows to return (default 25, max 100) |
| since | string | Earliest event date (YYYY-MM-DD, YYYY-MM or YYYY), inclusive |
| until | string | Latest event date, inclusive |
| where | object |
One ticker across every ticker-bearing Market Trackers dataset for one year (default: the current year): insider transactions, congressional trades, 13F holdings, federal contracts and grants, lobbying filings by the company, short-sale volume, clinical trials, FDA events, patents, Wikipedia pageviews. Returns per-dataset match counts with the newest rows of each — a public-record dossier from primary sources. Deep-history archive years too large for one fan-out are listed under skipped with the trackers_query call that reads them.
| Argument | Type | Description |
|---|---|---|
| year | integer | Event year to read (default: the current year) |
| limit | integer | Newest rows to include per dataset (default 5) |
| ticker* | string | Trading symbol, e.g. 'NVDA' |
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
| array |
| Journal account ids to scope to (from journal_list_accounts). Omit for every account, archived ones included. Unknown ids are rejected. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"context"
],
"properties": {
"to": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Inclusive end day (YYYY-MM-DD, journal timezone). Overrides `range`."
},
"from": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Inclusive start day (YYYY-MM-DD, journal timezone). Overrides `range`."
},
"range": {
"enum": [
"today",
"7d",
"30d",
"90d",
"365d",
"ytd",
"all"
],
"type": "string",
"description": "Named window ending today in the journal timezone. Ignored when from/to are given."
},
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
},
"accounts": {
"type": "array",
"items": {
"type": "string",
"minLength": 1
},
"maxItems": 50,
"minItems": 1,
"description": "Journal account ids to scope to (from journal_list_accounts). Omit for every account, archived ones included. Unknown ids are rejected."
}
}
}| limit | integer | Page size, default 25. |
| order | string | Default desc (largest / latest first); symbol defaults to asc (A→Z). |
| cursor | string | `nextCursor` from the previous page; keep every other argument identical. |
| status | string |
| symbol | string | One symbol, e.g. 'AAPL' (case-insensitive). |
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
| accounts | array | Journal account ids to scope to (from journal_list_accounts). Omit for every account, archived ones included. Unknown ids are rejected. |
| direction | string |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"context"
],
"properties": {
"to": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Inclusive end day (YYYY-MM-DD, journal timezone). Overrides `range`."
},
"tag": {
"type": "string",
"maxLength": 40,
"minLength": 1,
"description": "Trades carrying exactly this tag (see journal_list_tags)."
},
"from": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Inclusive start day (YYYY-MM-DD, journal timezone). Overrides `range`."
},
"sort": {
"enum": [
"openedAt",
"closedAt",
"netPnl",
"grossPnl",
"durationMs",
"quantity",
"symbol",
"rating"
],
"type": "string",
"description": "Field to order by; default openedAt. Trades without a value for it come last in either order."
},
"limit": {
"type": "integer",
"maximum": 100,
"minimum": 1,
"description": "Page size, default 25."
},
"order": {
"enum": [
"asc",
"desc"
],
"type": "string",
"description": "Default desc (largest / latest first); symbol defaults to asc (A→Z)."
},
"cursor": {
"type": "string",
"minLength": 1,
"description": "`nextCursor` from the previous page; keep every other argument identical."
},
"status": {
"enum": [
"open",
"win",
"loss",
"breakeven"
],
"type": "string"
},
"symbol": {
"type": "string",
"maxLength": 30,
"minLength": 1,
"description": "One symbol, e.g. 'AAPL' (case-insensitive)."
},
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
},
"accounts": {
"type": "array",
"items": {
"type": "string",
"minLength": 1
},
"maxItems": 50,
"minItems": 1,
"description": "Journal account ids to scope to (from journal_list_accounts). Omit for every account, archived ones included. Unknown ids are rejected."
},
"direction": {
"enum": [
"long",
"short"
],
"type": "string"
}
}
}| accounts | array | Journal account ids to scope to (from journal_list_accounts). Omit for every account, archived ones included. Unknown ids are rejected. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"context"
],
"properties": {
"to": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Inclusive end day (YYYY-MM-DD, journal timezone). Overrides `range`."
},
"from": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Inclusive start day (YYYY-MM-DD, journal timezone). Overrides `range`."
},
"range": {
"enum": [
"today",
"7d",
"30d",
"90d",
"365d",
"ytd",
"all"
],
"type": "string",
"description": "Named window ending today in the journal timezone. Ignored when from/to are given."
},
"compare": {
"type": "boolean",
"description": "Also compute the equal-length window immediately before this one."
},
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
},
"accounts": {
"type": "array",
"items": {
"type": "string",
"minLength": 1
},
"maxItems": 50,
"minItems": 1,
"description": "Journal account ids to scope to (from journal_list_accounts). Omit for every account, archived ones included. Unknown ids are rejected."
}
}
}| accounts | array | Journal account ids to scope to (from journal_list_accounts). Omit for every account, archived ones included. Unknown ids are rejected. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"context"
],
"properties": {
"q": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "Substring to look for in note text, case-insensitive."
},
"to": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Inclusive end day (YYYY-MM-DD, journal timezone). Overrides `range`."
},
"from": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Inclusive start day (YYYY-MM-DD, journal timezone). Overrides `range`."
},
"limit": {
"type": "integer",
"maximum": 100,
"minimum": 1,
"description": "Page size, default 25."
},
"cursor": {
"type": "string",
"minLength": 1,
"description": "`nextCursor` from the previous page; keep every other argument identical."
},
"symbol": {
"type": "string",
"maxLength": 30,
"minLength": 1
},
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
},
"accounts": {
"type": "array",
"items": {
"type": "string",
"minLength": 1
},
"maxItems": 50,
"minItems": 1,
"description": "Journal account ids to scope to (from journal_list_accounts). Omit for every account, archived ones included. Unknown ids are rejected."
}
}
}| mistakes | any |
| reviewed | boolean | Mark the trade reviewed (true) or not (false). |
| stopLoss | number | null | Planned stop price; null clears it. |
| playbookId | any | Playbook / setup name this trade followed; null clears it. |
| removeTags | array | Tags to remove (case-insensitive). |
| addMistakes | array | Mistakes to add. |
| profitTarget | number | null | Planned target price; null clears it. |
| removeMistakes | array | Mistakes to remove (case-insensitive). |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"key",
"context"
],
"properties": {
"key": {
"type": "string",
"minLength": 1,
"description": "The trade's `key` exactly as returned by journal_list_trades, journal_get_day, journal_search_notes or journal_add_trade. Never construct one."
},
"tags": {
"anyOf": [
{
"type": "array",
"items": {
"type": "string",
"maxLength": 40,
"minLength": 1
},
"maxItems": 20,
"description": "Replace the whole tag list; null clears it. Not with addTags/removeTags."
},
{
"type": "null"
}
]
},
"notes": {
"anyOf": [
{
"type": "string",
"maxLength": 20000
},
{
"type": "null"
}
],
"description": "Replaces the trade's note text; null clears it."
},
"rating": {
"anyOf": [
{
"type": "integer",
"maximum": 5,
"minimum": 1
},
{
"type": "null"
}
],
"description": "Execution quality 1–5; null clears it."
},
"addTags": {
"type": "array",
"items": {
"type": "string",
"maxLength": 40,
"minLength": 1
},
"maxItems": 20,
"description": "Tags to add (existing ones are kept; case-insensitive duplicates are ignored)."
},
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
},
"mistakes": {
"anyOf": [
{
"type": "array",
"items": {
"type": "string",
"maxLength": 80,
"minLength": 1
},
"maxItems": 20,
"description": "Replace the whole mistakes list; null clears it. Not with addMistakes/removeMistakes."
},
{
"type": "null"
}
]
},
"reviewed": {
"type": "boolean",
"description": "Mark the trade reviewed (true) or not (false)."
},
"stopLoss": {
"type": [
"number",
"null"
],
"description": "Planned stop price; null clears it."
},
"playbookId": {
"anyOf": [
{
"type": "string",
"maxLength": 100
},
{
"type": "null"
}
],
"description": "Playbook / setup name this trade followed; null clears it."
},
"removeTags": {
"type": "array",
"items": {
"type": "string",
"maxLength": 40,
"minLength": 1
},
"maxItems": 20,
"description": "Tags to remove (case-insensitive)."
},
"addMistakes": {
"type": "array",
"items": {
"type": "string",
"maxLength": 80,
"minLength": 1
},
"maxItems": 20,
"description": "Mistakes to add."
},
"profitTarget": {
"type": [
"number",
"null"
],
"description": "Planned target price; null clears it."
},
"removeMistakes": {
"type": "array",
"items": {
"type": "string",
"maxLength": 80,
"minLength": 1
},
"maxItems": 20,
"description": "Mistakes to remove (case-insensitive)."
}
}
}| platform | string | Trading platform the indicator supports, e.g. 'metatrader' |
| direction | string |
| page_size | integer | Default 24 |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"context"
],
"properties": {
"page": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0,
"description": "Default 0"
},
"sort": {
"enum": [
"name",
"date",
"family"
],
"type": "string",
"description": "Default: date"
},
"tags": {
"type": "array",
"items": {
"type": "string"
},
"description": "Tag ids (from library_list_tags); an indicator must carry every tag"
},
"text": {
"type": "string",
"description": "Server-side text filter"
},
"tier": {
"enum": [
"essential",
"premium",
"ultimate",
"ultra"
],
"type": "string",
"description": "Only indicators included in this LuxAlgo plan tier"
},
"family": {
"enum": [
"trend",
"momentum",
"volatility",
"volume-orderflow",
"market-structure",
"smc-ict",
"wyckoff",
"elliott-harmonics",
"patterns",
"levels",
"statistics",
"machine-learning",
"time-seasonality",
"sentiment-breadth",
"risk-exits",
"meta-composition",
"validation"
],
"type": "string"
},
"concept": {
"type": "string",
"description": "Concept slug — only indicators linked to this concept, e.g. 'rsi'"
},
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
},
"platform": {
"type": "string",
"description": "Trading platform the indicator supports, e.g. 'metatrader'"
},
"direction": {
"enum": [
"asc",
"desc"
],
"type": "string"
},
"page_size": {
"type": "integer",
"maximum": 100,
"minimum": 1,
"description": "Default 24"
}
}
}{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"query",
"context"
],
"properties": {
"type": {
"enum": [
"all",
"concepts",
"indicators"
],
"type": "string",
"description": "Limit to 'concepts' (explanations) or 'indicators' (implementations); default all"
},
"limit": {
"type": "integer",
"maximum": 50,
"minimum": 1,
"description": "Max results (default 10)"
},
"query": {
"type": "string",
"minLength": 1,
"description": "A concept, indicator name, alias, or topic — e.g. 'order blocks', 'mean reversion', 'stochastics'"
},
"family": {
"enum": [
"trend",
"momentum",
"volatility",
"volume-orderflow",
"market-structure",
"smc-ict",
"wyckoff",
"elliott-harmonics",
"patterns",
"levels",
"statistics",
"machine-learning",
"time-seasonality",
"sentiment-breadth",
"risk-exits",
"meta-composition",
"validation"
],
"type": "string",
"description": "Narrow to one concept family"
},
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
}
}
}| Argument | Type | Description |
|---|---|---|
| firmId* | string | Directory firm id or firm name from propfirms_list_simulatable, e.g. 'ftmo'. |
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
| challengeId* | string | Directory challenge id from propfirms_list_simulatable. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"firmId",
"challengeId",
"context"
],
"properties": {
"firmId": {
"type": "string",
"minLength": 1,
"description": "Directory firm id or firm name from propfirms_list_simulatable, e.g. 'ftmo'."
},
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
},
"challengeId": {
"type": "string",
"minLength": 1,
"description": "Directory challenge id from propfirms_list_simulatable."
}
}
}| paths | integer | Monte Carlo paths (independent simulated trader journeys). Default 10,000 (well under a second); capped at 100,000 per tool call. Confidence intervals shrink roughly with the square root of paths. |
| avgWinR* | number | Average winning trade in R-multiples, i.e. multiples of the amount risked per trade (1.5 = winners average 1.5x the risk). |
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
| winRate* | number | Probability a trade is a winner, as a FRACTION in [0, 1] (0.55 = 55% winners) - NOT percent units. The most impactful input: traders routinely overestimate it by a few points, which can flip EV negative, so prefer measured stats over self-reported ones. |
| winStdR | number | Standard deviation of winner sizes in R (0 = every winner is exactly avgWinR). Default 0. Adding spread makes streak damage more realistic. |
| avgLossR | number | Average losing trade in R, as a POSITIVE number. Default 1 (losers lose exactly the risked amount, i.e. stops are honored). Raise above 1 to model slippage or blown stops. |
| lossStdR | number | Standard deviation of loser sizes in R (0 = every loser is exactly avgLossR). Default 0. |
| riskMode | string | How riskValue is interpreted. 'percent-of-balance' (default): risk compounds with the current balance. 'percent-of-initial': constant currency risk derived from the initial account size - how most prop traders size, since loss limits are fixed in currency. 'fixed-amount': explicit currency risked per 1R. |
| riskValue* | number | Risk per trade - the value of 1R. PERCENT UNITS for percent modes (0.5 = 0.5% risked per trade; a typical prop range is 0.25-2), or a currency amount for 'fixed-amount'. NOT a fraction. |
| attemptCap | integer | Maximum challenge attempts per path before that path gives up. Default 25. Journey statistics (expected attempts/cost, P(funded)) are censored at this cap. |
| challenges* | array | The challenges to simulate this trader across (1-12 entries; 2+ for a meaningful comparison). Mix dataset references and inline specs freely. |
| tradesPerDay* | number | Average trades per simulated trading day. More trades per day means more ways to hit the daily loss limit within a single day. |
| simulateFunded | boolean | Whether to simulate the funded stage (payouts, blowup risk) after passing. Default true - EV is only meaningful with it on; set false to study the evaluation alone. |
| fundedHorizonDays | integer | Funded-stage horizon in trading days for the payout/EV simulation. Default 90 (about 4 calendar months). EV scales with this choice - state it when reporting EV. |
| tradesPerDayModel | string | 'fixed' (default): the same count every day. 'poisson': daily count drawn Poisson(tradesPerDay); days can then have zero trades, which do not count as trading days. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"challenges",
"winRate",
"avgWinR",
"tradesPerDay",
"riskValue",
"context"
],
"properties": {
"seed": {
"anyOf": [
{
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991
},
{
"type": "string"
}
],
"description": "RNG seed (integer or string). Default 42. Same inputs + seed reproduce byte-identical results - include the seed when reporting so users can reproduce the numbers."
},
"paths": {
"type": "integer",
"maximum": 100000,
"minimum": 100,
"description": "Monte Carlo paths (independent simulated trader journeys). Default 10,000 (well under a second); capped at 100,000 per tool call. Confidence intervals shrink roughly with the square root of paths."
},
"avgWinR": {
"type": "number",
"description": "Average winning trade in R-multiples, i.e. multiples of the amount risked per trade (1.5 = winners average 1.5x the risk).",
"exclusiveMinimum": 0
},
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
},
"winRate": {
"type": "number",
"maximum": 1,
"minimum": 0,
"description": "Probability a trade is a winner, as a FRACTION in [0, 1] (0.55 = 55% winners) - NOT percent units. The most impactful input: traders routinely overestimate it by a few points, which can flip EV negative, so prefer measured stats over self-reported ones."
},
"winStdR": {
"type": "number",
"minimum": 0,
"description": "Standard deviation of winner sizes in R (0 = every winner is exactly avgWinR). Default 0. Adding spread makes streak damage more realistic."
},
"avgLossR": {
"type": "number",
"description": "Average losing trade in R, as a POSITIVE number. Default 1 (losers lose exactly the risked amount, i.e. stops are honored). Raise above 1 to model slippage or blown stops.",
"exclusiveMinimum": 0
},
"lossStdR": {
"type": "number",
"minimum": 0,
"description": "Standard deviation of loser sizes in R (0 = every loser is exactly avgLossR). Default 0."
},
"riskMode": {
"enum": [
"percent-of-balance",
"percent-of-initial",
"fixed-amount"
],
"type": "string",
"description": "How riskValue is interpreted. 'percent-of-balance' (default): risk compounds with the current balance. 'percent-of-initial': constant currency risk derived from the initial account size - how most prop traders size, since loss limits are fixed in currency. 'fixed-amount': explicit currency risked per 1R."
},
"riskValue": {
"type": "number",
"description": "Risk per trade - the value of 1R. PERCENT UNITS for percent modes (0.5 = 0.5% risked per trade; a typical prop range is 0.25-2), or a currency amount for 'fixed-amount'. NOT a fraction.",
"exclusiveMinimum": 0
},
"attemptCap": {
"type": "integer",
"maximum": 1000,
"minimum": 1,
"description": "Maximum challenge attempts per path before that path gives up. Default 25. Journey statistics (expected attempts/cost, P(funded)) are censored at this cap."
},
"challenges": {
"type": "array",
"items": {
"type": "object",
"properties": {
"spec": {
"type": "object",
"required": [
"challengeId",
"name",
"accountSize",
"steps",
"dailyLoss",
"maxLoss",
"fees",
"funded"
],
"properties": {
"fees": {
"type": "object",
"required": [
"price"
],
"properties": {
"price": {
"type": "number",
"minimum": 0,
"description": "Challenge price in account currency. Under 'monthly' billing: price per month."
},
"billing": {
"enum": [
"one-time",
"monthly"
],
"type": "string",
"description": "'one-time' (default): the price buys one attempt; failed attempts are re-bought or reset. 'monthly': recurring subscription while evaluating (common for futures firms)."
},
"resetFee": {
"anyOf": [
{
"type": "number",
"minimum": 0
},
{
"type": "null"
}
],
"description": "Discounted fee to reset a failed attempt. null (default) = no reset offer: a failed one-time attempt costs full price again; a failed monthly attempt rides on the subscription."
},
"activationFee": {
"type": "number",
"minimum": 0,
"description": "One-time fee charged when the funded account is activated. Default 0."
},
"refundableOnPass": {
"type": "boolean",
"description": "Whether the one-time challenge fee is refunded once funded (credited back in cost/EV). Default false."
}
},
"description": "Fees - everything that goes into expected total cost.",
"additionalProperties": {}
},
"name": {
"type": "string",
"minLength": 1,
"description": "Display name, e.g. '100K 2-Step'."
},
"steps": {
"type": "array",
"items": {
"type": "object",
"properties": {
"maxDays": {
"anyOf": [
{
"type": "integer",
"maximum": 9007199254740991,
"exclusiveMinimum": 0
},
{
"type": "null"
}
],
"description": "Trading-day limit for the step; null (the default) = unlimited time."
},
"maxLoss": {
"type": "object",
"required": [
"mode"
],
"properties": {
"pct": {
"type": "number",
"maximum": 100,
"description": "Max loss in PERCENT UNITS of the initial account size (10 = 10%). Exactly one of pct/amount.",
"exclusiveMinimum": 0
},
"mode": {
"enum": [
"static-initial",
"trailing-realized-eod",
"trailing-intraday-unrealized",
"trailing-locks-at-initial"
],
"type": "string",
"description": "How the max-loss floor behaves - the single most consequential rule difference between firms. 'static-initial': floor fixed at initial balance minus the limit; never moves (classic CFD two-step). 'trailing-realized-eod': floor ratchets up with end-of-day balance highs; intraday highs do not move it. 'trailing-intraday-unrealized': floor trails the peak unrealized equity intraday and never stops trailing (futures-style; the most-miscalculated rule in the industry: it cuts pass probability dramatically). 'trailing-locks-at-initial': trails intraday peak equity until the floor reaches the initial balance, then freezes (common futures variant). Locking is also composable: locksAtInitial adds the same lock to an EOD trail, and lockOffsetAmount shifts the lock level to initial balance + that amount (e.g. 100 models 'stops trailing $100 above the start')."
},
"amount": {
"type": "number",
"description": "Max loss as a fixed currency amount (alternative to pct).",
"exclusiveMinimum": 0
},
"locksAtInitial": {
"type": "boolean",
"description": "For trailing modes: once the trailing floor climbs up to the initial balance (plus lockOffsetAmount), it locks there and stops trailing. Default false. 'trailing-locks-at-initial' locks by definition; set this to add the same lock to 'trailing-realized-eod' (e.g. an EOD trail that stops at the starting balance)."
},
"lockOffsetAmount": {
"type": "number",
"minimum": 0,
"description": "Currency offset of the lock level: the floor locks at initial balance + this amount, modeling rules like 'the trailing threshold stops $100 above the start'. Default 0. Only meaningful when the rule locks (mode 'trailing-locks-at-initial' or locksAtInitial=true)."
}
},
"description": "Per-step override of the challenge-level max loss rule. Omit to inherit.",
"additionalProperties": {}
},
"dailyLoss": {
"anyOf": [
{
"type": "object",
"properties": {
"pct": {
"type": "number",
"maximum": 100,
"description": "Daily loss limit in PERCENT UNITS (5 = 5%); what it is a percent OF is set by limitBasis. Exactly one of pct/amount.",
"exclusiveMinimum": 0
},
"basis": {
"enum": [
"prior-day-balance",
"prior-day-equity"
],
"type": "string",
"description": "Anchor today's loss is measured from: prior day's closing balance or closing equity (they differ only with overnight positions). Default 'prior-day-balance'."
},
"amount": {
"type": "number",
"description": "Daily loss limit as a fixed currency amount (alternative to pct).",
"exclusiveMinimum": 0
},
"evaluation": {
"enum": [
"intraday",
"end-of-day"
],
"type": "string",
"description": "'intraday': fails the moment equity touches the daily floor. 'end-of-day': only the close is checked. Default 'intraday'."
},
"limitBasis": {
"enum": [
"initial-balance",
"anchor"
],
"type": "string",
"description": "What a percentage limit is a percent OF. 'initial-balance': a fixed currency allowance (always e.g. 5% of the starting account). 'anchor': recomputed daily from the day's anchor. Default 'initial-balance'."
},
"includesOpenPnl": {
"type": "boolean",
"description": "Whether floating (unrealized) P&L counts toward the daily loss, i.e. breach can happen intra-position. Default true."
}
},
"description": "Daily loss rule: the daily floor is anchor minus limit, reset at each trading-day boundary. Exactly one of pct/amount must be set.",
"additionalProperties": {}
},
{
"type": "null"
}
],
"description": "Per-step override of the challenge-level daily loss rule. Omit to inherit; null = no daily loss rule in this step."
},
"consistency": {
"anyOf": [
{
"type": "object",
"required": [
"maxBestDayProfitPct"
],
"properties": {
"maxBestDayProfitPct": {
"type": "number",
"maximum": 100,
"description": "Maximum share of the step's total profit the best single day may contribute, in PERCENT UNITS (40 = the best day may be at most 40% of total profit).",
"exclusiveMinimum": 0
}
},
"additionalProperties": {}
},
{
"type": "null"
}
],
"description": "Consistency rule - SIMULATED (engine v1), not just flagged: one outsized day effectively raises the target (total profit must reach best day / pct), and the simulated trader keeps trading - rationally stopping days early when that helps - until the best-day share complies (see flag 'consistency-stop-rule'). null or omitted = no consistency rule."
},
"minTradingDays": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0,
"description": "Minimum days with at least one trade before the step can be passed. Default 0."
},
"profitTargetPct": {
"type": "number",
"description": "Profit target in PERCENT UNITS of the initial account size (8 = 8%). Exactly one of profitTargetPct/profitTargetAmount.",
"exclusiveMinimum": 0
},
"profitTargetAmount": {
"type": "number",
"description": "Profit target as a fixed currency amount (alternative to profitTargetPct).",
"exclusiveMinimum": 0
}
},
"description": "One evaluation step. Each step starts on a fresh account at the initial balance.",
"additionalProperties": {}
},
"minItems": 1,
"description": "Evaluation steps in order. Passing the last step means funded."
},
"funded": {
"type": "object",
"required": [
"profitSplitPct",
"payoutFrequency"
],
"properties": {
"notes": {
"type": "string",
"description": "Free-text funded-stage details that are not simulated."
},
"maxLoss": {
"type": "object",
"required": [
"mode"
],
"properties": {
"pct": {
"type": "number",
"maximum": 100,
"description": "Max loss in PERCENT UNITS of the initial account size (10 = 10%). Exactly one of pct/amount.",
"exclusiveMinimum": 0
},
"mode": {
"enum": [
"static-initial",
"trailing-realized-eod",
"trailing-intraday-unrealized",
"trailing-locks-at-initial"
],
"type": "string",
"description": "How the max-loss floor behaves - the single most consequential rule difference between firms. 'static-initial': floor fixed at initial balance minus the limit; never moves (classic CFD two-step). 'trailing-realized-eod': floor ratchets up with end-of-day balance highs; intraday highs do not move it. 'trailing-intraday-unrealized': floor trails the peak unrealized equity intraday and never stops trailing (futures-style; the most-miscalculated rule in the industry: it cuts pass probability dramatically). 'trailing-locks-at-initial': trails intraday peak equity until the floor reaches the initial balance, then freezes (common futures variant). Locking is also composable: locksAtInitial adds the same lock to an EOD trail, and lockOffsetAmount shifts the lock level to initial balance + that amount (e.g. 100 models 'stops trailing $100 above the start')."
},
"amount": {
"type": "number",
"description": "Max loss as a fixed currency amount (alternative to pct).",
"exclusiveMinimum": 0
},
"locksAtInitial": {
"type": "boolean",
"description": "For trailing modes: once the trailing floor climbs up to the initial balance (plus lockOffsetAmount), it locks there and stops trailing. Default false. 'trailing-locks-at-initial' locks by definition; set this to add the same lock to 'trailing-realized-eod' (e.g. an EOD trail that stops at the starting balance)."
},
"lockOffsetAmount": {
"type": "number",
"minimum": 0,
"description": "Currency offset of the lock level: the floor locks at initial balance + this amount, modeling rules like 'the trailing threshold stops $100 above the start'. Default 0. Only meaningful when the rule locks (mode 'trailing-locks-at-initial' or locksAtInitial=true)."
}
},
"description": "Funded-account override of the max loss rule. Omit to inherit.",
"additionalProperties": {}
},
"dailyLoss": {
"anyOf": [
{
"type": "object",
"properties": {
"pct": {
"type": "number",
"maximum": 100,
"description": "Daily loss limit in PERCENT UNITS (5 = 5%); what it is a percent OF is set by limitBasis. Exactly one of pct/amount.",
"exclusiveMinimum": 0
},
"basis": {
"enum": [
"prior-day-balance",
"prior-day-equity"
],
"type": "string",
"description": "Anchor today's loss is measured from: prior day's closing balance or closing equity (they differ only with overnight positions). Default 'prior-day-balance'."
},
"amount": {
"type": "number",
"description": "Daily loss limit as a fixed currency amount (alternative to pct).",
"exclusiveMinimum": 0
},
"evaluation": {
"enum": [
"intraday",
"end-of-day"
],
"type": "string",
"description": "'intraday': fails the moment equity touches the daily floor. 'end-of-day': only the close is checked. Default 'intraday'."
},
"limitBasis": {
"enum": [
"initial-balance",
"anchor"
],
"type": "string",
"description": "What a percentage limit is a percent OF. 'initial-balance': a fixed currency allowance (always e.g. 5% of the starting account). 'anchor': recomputed daily from the day's anchor. Default 'initial-balance'."
},
"includesOpenPnl": {
"type": "boolean",
"description": "Whether floating (unrealized) P&L counts toward the daily loss, i.e. breach can happen intra-position. Default true."
}
},
"description": "Daily loss rule: the daily floor is anchor minus limit, reset at each trading-day boundary. Exactly one of pct/amount must be set.",
"additionalProperties": {}
},
{
"type": "null"
}
],
"description": "Funded-account override of the daily loss rule. Omit to inherit; null = none."
},
"payoutRules": {
"type": "object",
"properties": {
"bufferAmount": {
"type": "number",
"minimum": 0,
"description": "Profit buffer that must remain in the account; only profit above it is withdrawable. Default 0."
},
"minWinningDays": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0,
"description": "Winning days required in a payout window before a payout can be requested. Default 0."
},
"maxPayoutAmount": {
"type": "number",
"description": "Absolute currency cap per payout request. Omit for no fixed cap.",
"exclusiveMinimum": 0
},
"winningDayMinProfit": {
"type": "number",
"minimum": 0,
"description": "Minimum profit for a day to count as a winning day. Default 0 (any positive day)."
},
"maxPayoutPctOfProfit": {
"type": "number",
"maximum": 100,
"description": "Cap on each payout in PERCENT UNITS of accrued profit (50 = at most half the profit per request). Omit for no percentage cap.",
"exclusiveMinimum": 0
},
"consistencyMaxBestDayPct": {
"type": "number",
"maximum": 100,
"description": "Funded consistency gate in PERCENT UNITS: the best day may contribute at most this share of the payout window's profit. Evaluated per window (see flag 'funded-consistency-window-approximated').",
"exclusiveMinimum": 0
}
},
"description": "Payout gating - SIMULATED (engine v1), not just flagged: a payout happens only when these conditions are met, and on each eligible payout day the trader withdraws the maximum the rules allow (profit above the buffer, under the caps, never below the loss floor); balances and loss floors carry across payouts (see flag 'funded-withdrawal-model'). Omit for ungated payouts.",
"additionalProperties": {}
},
"profitSplitPct": {
"type": "number",
"maximum": 100,
"minimum": 0,
"description": "Trader's share of funded profits in PERCENT UNITS (80 = 80%)."
},
"payoutFrequency": {
"enum": [
"weekly",
"biweekly",
"monthly",
"on-demand"
],
"type": "string",
"description": "How often funded profits can be withdrawn."
},
"firstPayoutMinDays": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0,
"description": "Minimum days on the funded account before the first payout. Default 0."
}
},
"description": "Funded-stage terms used for the payout/EV simulation.",
"additionalProperties": {}
},
"maxLoss": {
"type": "object",
"required": [
"mode"
],
"properties": {
"pct": {
"type": "number",
"maximum": 100,
"description": "Max loss in PERCENT UNITS of the initial account size (10 = 10%). Exactly one of pct/amount.",
"exclusiveMinimum": 0
},
"mode": {
"enum": [
"static-initial",
"trailing-realized-eod",
"trailing-intraday-unrealized",
"trailing-locks-at-initial"
],
"type": "string",
"description": "How the max-loss floor behaves - the single most consequential rule difference between firms. 'static-initial': floor fixed at initial balance minus the limit; never moves (classic CFD two-step). 'trailing-realized-eod': floor ratchets up with end-of-day balance highs; intraday highs do not move it. 'trailing-intraday-unrealized': floor trails the peak unrealized equity intraday and never stops trailing (futures-style; the most-miscalculated rule in the industry: it cuts pass probability dramatically). 'trailing-locks-at-initial': trails intraday peak equity until the floor reaches the initial balance, then freezes (common futures variant). Locking is also composable: locksAtInitial adds the same lock to an EOD trail, and lockOffsetAmount shifts the lock level to initial balance + that amount (e.g. 100 models 'stops trailing $100 above the start')."
},
"amount": {
"type": "number",
"description": "Max loss as a fixed currency amount (alternative to pct).",
"exclusiveMinimum": 0
},
"locksAtInitial": {
"type": "boolean",
"description": "For trailing modes: once the trailing floor climbs up to the initial balance (plus lockOffsetAmount), it locks there and stops trailing. Default false. 'trailing-locks-at-initial' locks by definition; set this to add the same lock to 'trailing-realized-eod' (e.g. an EOD trail that stops at the starting balance)."
},
"lockOffsetAmount": {
"type": "number",
"minimum": 0,
"description": "Currency offset of the lock level: the floor locks at initial balance + this amount, modeling rules like 'the trailing threshold stops $100 above the start'. Default 0. Only meaningful when the rule locks (mode 'trailing-locks-at-initial' or locksAtInitial=true)."
}
},
"description": "Challenge-level max loss rule applied to every step unless a step overrides it. Required.",
"additionalProperties": {}
},
"sources": {
"type": "array",
"items": {
"type": "object",
"required": [
"url",
"lastVerified"
],
"properties": {
"url": {
"type": "string",
"description": "Public page documenting the rule."
},
"note": {
"type": "string"
},
"lastVerified": {
"type": "string",
"description": "ISO date the rules were last checked against that page."
}
},
"additionalProperties": {}
},
"description": "Public citations. Optional for inline specs; dataset entries always carry them."
},
"currency": {
"type": "string",
"description": "ISO currency code all amounts are denominated in. Default USD."
},
"dailyLoss": {
"anyOf": [
{
"type": "object",
"properties": {
"pct": {
"type": "number",
"maximum": 100,
"description": "Daily loss limit in PERCENT UNITS (5 = 5%); what it is a percent OF is set by limitBasis. Exactly one of pct/amount.",
"exclusiveMinimum": 0
},
"basis": {
"enum": [
"prior-day-balance",
"prior-day-equity"
],
"type": "string",
"description": "Anchor today's loss is measured from: prior day's closing balance or closing equity (they differ only with overnight positions). Default 'prior-day-balance'."
},
"amount": {
"type": "number",
"description": "Daily loss limit as a fixed currency amount (alternative to pct).",
"exclusiveMinimum": 0
},
"evaluation": {
"enum": [
"intraday",
"end-of-day"
],
"type": "string",
"description": "'intraday': fails the moment equity touches the daily floor. 'end-of-day': only the close is checked. Default 'intraday'."
},
"limitBasis": {
"enum": [
"initial-balance",
"anchor"
],
"type": "string",
"description": "What a percentage limit is a percent OF. 'initial-balance': a fixed currency allowance (always e.g. 5% of the starting account). 'anchor': recomputed daily from the day's anchor. Default 'initial-balance'."
},
"includesOpenPnl": {
"type": "boolean",
"description": "Whether floating (unrealized) P&L counts toward the daily loss, i.e. breach can happen intra-position. Default true."
}
},
"description": "Daily loss rule: the daily floor is anchor minus limit, reset at each trading-day boundary. Exactly one of pct/amount must be set.",
"additionalProperties": {}
},
{
"type": "null"
}
],
"description": "Challenge-level daily loss rule applied to every step unless a step overrides it. null = no daily loss rule. This field is required (pass null explicitly for none)."
},
"accountSize": {
"type": "number",
"description": "Initial account balance in account currency.",
"exclusiveMinimum": 0
},
"challengeId": {
"type": "string",
"minLength": 1,
"description": "Stable kebab-case id for this ruleset, e.g. '100k-2step'."
},
"constraints": {
"type": "object",
"description": "Informational trading constraints (maxLeverage, newsTrading, weekendHolding, ...). Recorded and flagged, never simulated.",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
},
"productType": {
"enum": [
"futures",
"cfd",
"equities"
],
"type": "string",
"description": "Instrument class the challenge is traded on: 'futures', 'cfd' (forex/CFD), or 'equities'."
},
"flagsNotSimulated": {
"type": "array",
"items": {
"type": "string"
},
"description": "Honesty channel: ids of rules this entry has that the engine does not simulate (e.g. 'scaling-plan', 'soft-daily-lockout'). Surfaced in every result's assumption flags. Consistency rules and payout gating do NOT belong here - the engine simulates them."
}
},
"description": "Inline challenge ruleset, for challenges not in the directory or for what-if rule edits. Mutually exclusive with firmId/challengeId. Identify the challenge EITHER by directory reference (firmId + challengeId, discovered via propfirms_list_simulatable; firmId accepts the directory id or the firm's name) OR by a full inline `spec` object - the exact shape propfirms_challenge_rules returns, so you can fetch a directory entry, change one rule, and re-simulate to model rule variations. Provide exactly one of the two forms; providing both or neither is an error. Directory references need network access; inline specs are fully offline.",
"additionalProperties": {}
},
"firmId": {
"type": "string",
"minLength": 1,
"description": "Directory firm id or firm name (e.g. 'ftmo' or 'FTMO'); discover with propfirms_list_simulatable. Must be paired with challengeId. Mutually exclusive with `spec`."
},
"challengeId": {
"type": "string",
"minLength": 1,
"description": "Directory challenge id; discover with propfirms_list_simulatable. Must be paired with firmId. Mutually exclusive with `spec`."
}
},
"description": "One challenge: either firmId + challengeId (dataset) or an inline spec."
},
"maxItems": 12,
"minItems": 1,
"description": "The challenges to simulate this trader across (1-12 entries; 2+ for a meaningful comparison). Mix dataset references and inline specs freely."
},
"tradesPerDay": {
"type": "number",
"description": "Average trades per simulated trading day. More trades per day means more ways to hit the daily loss limit within a single day.",
"exclusiveMinimum": 0
},
"simulateFunded": {
"type": "boolean",
"description": "Whether to simulate the funded stage (payouts, blowup risk) after passing. Default true - EV is only meaningful with it on; set false to study the evaluation alone."
},
"fundedHorizonDays": {
"type": "integer",
"maximum": 2000,
"minimum": 1,
"description": "Funded-stage horizon in trading days for the payout/EV simulation. Default 90 (about 4 calendar months). EV scales with this choice - state it when reporting EV."
},
"tradesPerDayModel": {
"enum": [
"fixed",
"poisson"
],
"type": "string",
"description": "'fixed' (default): the same count every day. 'poisson': daily count drawn Poisson(tradesPerDay); days can then have zero trades, which do not count as trading days."
}
}
}| productType | string | Optional filter to one instrument class. Omit to list every firm. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"context"
],
"properties": {
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
},
"productType": {
"enum": [
"futures",
"cfd"
],
"type": "string",
"description": "Optional filter to one instrument class. Omit to list every firm."
}
}
}| Type |
|---|
| Description |
|---|
| max | number | Grid end, same units as min. Default 3 (= 3% per trade for percent modes). |
| min | number | Grid start, in the risk units of riskMode (percent units for percent modes, currency for 'fixed-amount'). Default 0.1 (= 0.1% per trade for percent modes). |
| seed | any | RNG seed (integer or string). Default 42. Same inputs + seed reproduce byte-identical results - include the seed when reporting so users can reproduce the numbers. |
| spec | object | Inline challenge ruleset, for challenges not in the directory or for what-if rule edits. Mutually exclusive with firmId/challengeId. Identify the challenge EITHER by directory reference (firmId + challengeId, discovered via propfirms_list_simulatable; firmId accepts the directory id or the firm's name) OR by a full inline `spec` object - the exact shape propfirms_challenge_rules returns, so you can fetch a directory entry, change one rule, and re-simulate to model rule variations. Provide exactly one of the two forms; providing both or neither is an error. Directory references need network access; inline specs are fully offline. |
| step | number | Grid step, same units. Default 0.1. The sweep runs one full simulation per grid point, so (max - min) / step + 1 simulations in total - keep the grid coarse or paths low for a first pass. |
| paths | integer | Monte Carlo paths (independent simulated trader journeys). Default 10,000 (well under a second); capped at 100,000 per tool call. Confidence intervals shrink roughly with the square root of paths. |
| firmId | string | Directory firm id or firm name (e.g. 'ftmo' or 'FTMO'); discover with propfirms_list_simulatable. Must be paired with challengeId. Mutually exclusive with `spec`. |
| avgWinR* | number | Average winning trade in R-multiples, i.e. multiples of the amount risked per trade (1.5 = winners average 1.5x the risk). |
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
| winRate* | number | Probability a trade is a winner, as a FRACTION in [0, 1] (0.55 = 55% winners) - NOT percent units. The most impactful input: traders routinely overestimate it by a few points, which can flip EV negative, so prefer measured stats over self-reported ones. |
| winStdR | number | Standard deviation of winner sizes in R (0 = every winner is exactly avgWinR). Default 0. Adding spread makes streak damage more realistic. |
| avgLossR | number | Average losing trade in R, as a POSITIVE number. Default 1 (losers lose exactly the risked amount, i.e. stops are honored). Raise above 1 to model slippage or blown stops. |
| lossStdR | number | Standard deviation of loser sizes in R (0 = every loser is exactly avgLossR). Default 0. |
| riskMode | string | How riskValue is interpreted. 'percent-of-balance' (default): risk compounds with the current balance. 'percent-of-initial': constant currency risk derived from the initial account size - how most prop traders size, since loss limits are fixed in currency. 'fixed-amount': explicit currency risked per 1R. |
| attemptCap | integer | Maximum challenge attempts per path before that path gives up. Default 25. Journey statistics (expected attempts/cost, P(funded)) are censored at this cap. |
| challengeId | string | Directory challenge id; discover with propfirms_list_simulatable. Must be paired with firmId. Mutually exclusive with `spec`. |
| tradesPerDay* | number | Average trades per simulated trading day. More trades per day means more ways to hit the daily loss limit within a single day. |
| simulateFunded | boolean | Whether to simulate the funded stage (payouts, blowup risk) after passing. Default true - EV is only meaningful with it on; set false to study the evaluation alone. |
| fundedHorizonDays | integer | Funded-stage horizon in trading days for the payout/EV simulation. Default 90 (about 4 calendar months). EV scales with this choice - state it when reporting EV. |
| tradesPerDayModel | string | 'fixed' (default): the same count every day. 'poisson': daily count drawn Poisson(tradesPerDay); days can then have zero trades, which do not count as trading days. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"winRate",
"avgWinR",
"tradesPerDay",
"context"
],
"properties": {
"max": {
"type": "number",
"description": "Grid end, same units as min. Default 3 (= 3% per trade for percent modes).",
"exclusiveMinimum": 0
},
"min": {
"type": "number",
"description": "Grid start, in the risk units of riskMode (percent units for percent modes, currency for 'fixed-amount'). Default 0.1 (= 0.1% per trade for percent modes).",
"exclusiveMinimum": 0
},
"seed": {
"anyOf": [
{
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991
},
{
"type": "string"
}
],
"description": "RNG seed (integer or string). Default 42. Same inputs + seed reproduce byte-identical results - include the seed when reporting so users can reproduce the numbers."
},
"spec": {
"type": "object",
"required": [
"challengeId",
"name",
"accountSize",
"steps",
"dailyLoss",
"maxLoss",
"fees",
"funded"
],
"properties": {
"fees": {
"type": "object",
"required": [
"price"
],
"properties": {
"price": {
"type": "number",
"minimum": 0,
"description": "Challenge price in account currency. Under 'monthly' billing: price per month."
},
"billing": {
"enum": [
"one-time",
"monthly"
],
"type": "string",
"description": "'one-time' (default): the price buys one attempt; failed attempts are re-bought or reset. 'monthly': recurring subscription while evaluating (common for futures firms)."
},
"resetFee": {
"anyOf": [
{
"type": "number",
"minimum": 0
},
{
"type": "null"
}
],
"description": "Discounted fee to reset a failed attempt. null (default) = no reset offer: a failed one-time attempt costs full price again; a failed monthly attempt rides on the subscription."
},
"activationFee": {
"type": "number",
"minimum": 0,
"description": "One-time fee charged when the funded account is activated. Default 0."
},
"refundableOnPass": {
"type": "boolean",
"description": "Whether the one-time challenge fee is refunded once funded (credited back in cost/EV). Default false."
}
},
"description": "Fees - everything that goes into expected total cost.",
"additionalProperties": {}
},
"name": {
"type": "string",
"minLength": 1,
"description": "Display name, e.g. '100K 2-Step'."
},
"steps": {
"type": "array",
"items": {
"type": "object",
"properties": {
"maxDays": {
"anyOf": [
{
"type": "integer",
"maximum": 9007199254740991,
"exclusiveMinimum": 0
},
{
"type": "null"
}
],
"description": "Trading-day limit for the step; null (the default) = unlimited time."
},
"maxLoss": {
"type": "object",
"required": [
"mode"
],
"properties": {
"pct": {
"type": "number",
"maximum": 100,
"description": "Max loss in PERCENT UNITS of the initial account size (10 = 10%). Exactly one of pct/amount.",
"exclusiveMinimum": 0
},
"mode": {
"enum": [
"static-initial",
"trailing-realized-eod",
"trailing-intraday-unrealized",
"trailing-locks-at-initial"
],
"type": "string",
"description": "How the max-loss floor behaves - the single most consequential rule difference between firms. 'static-initial': floor fixed at initial balance minus the limit; never moves (classic CFD two-step). 'trailing-realized-eod': floor ratchets up with end-of-day balance highs; intraday highs do not move it. 'trailing-intraday-unrealized': floor trails the peak unrealized equity intraday and never stops trailing (futures-style; the most-miscalculated rule in the industry: it cuts pass probability dramatically). 'trailing-locks-at-initial': trails intraday peak equity until the floor reaches the initial balance, then freezes (common futures variant). Locking is also composable: locksAtInitial adds the same lock to an EOD trail, and lockOffsetAmount shifts the lock level to initial balance + that amount (e.g. 100 models 'stops trailing $100 above the start')."
},
"amount": {
"type": "number",
"description": "Max loss as a fixed currency amount (alternative to pct).",
"exclusiveMinimum": 0
},
"locksAtInitial": {
"type": "boolean",
"description": "For trailing modes: once the trailing floor climbs up to the initial balance (plus lockOffsetAmount), it locks there and stops trailing. Default false. 'trailing-locks-at-initial' locks by definition; set this to add the same lock to 'trailing-realized-eod' (e.g. an EOD trail that stops at the starting balance)."
},
"lockOffsetAmount": {
"type": "number",
"minimum": 0,
"description": "Currency offset of the lock level: the floor locks at initial balance + this amount, modeling rules like 'the trailing threshold stops $100 above the start'. Default 0. Only meaningful when the rule locks (mode 'trailing-locks-at-initial' or locksAtInitial=true)."
}
},
"description": "Per-step override of the challenge-level max loss rule. Omit to inherit.",
"additionalProperties": {}
},
"dailyLoss": {
"anyOf": [
{
"type": "object",
"properties": {
"pct": {
"type": "number",
"maximum": 100,
"description": "Daily loss limit in PERCENT UNITS (5 = 5%); what it is a percent OF is set by limitBasis. Exactly one of pct/amount.",
"exclusiveMinimum": 0
},
"basis": {
"enum": [
"prior-day-balance",
"prior-day-equity"
],
"type": "string",
"description": "Anchor today's loss is measured from: prior day's closing balance or closing equity (they differ only with overnight positions). Default 'prior-day-balance'."
},
"amount": {
"type": "number",
"description": "Daily loss limit as a fixed currency amount (alternative to pct).",
"exclusiveMinimum": 0
},
"evaluation": {
"enum": [
"intraday",
"end-of-day"
],
"type": "string",
"description": "'intraday': fails the moment equity touches the daily floor. 'end-of-day': only the close is checked. Default 'intraday'."
},
"limitBasis": {
"enum": [
"initial-balance",
"anchor"
],
"type": "string",
"description": "What a percentage limit is a percent OF. 'initial-balance': a fixed currency allowance (always e.g. 5% of the starting account). 'anchor': recomputed daily from the day's anchor. Default 'initial-balance'."
},
"includesOpenPnl": {
"type": "boolean",
"description": "Whether floating (unrealized) P&L counts toward the daily loss, i.e. breach can happen intra-position. Default true."
}
},
"description": "Daily loss rule: the daily floor is anchor minus limit, reset at each trading-day boundary. Exactly one of pct/amount must be set.",
"additionalProperties": {}
},
{
"type": "null"
}
],
"description": "Per-step override of the challenge-level daily loss rule. Omit to inherit; null = no daily loss rule in this step."
},
"consistency": {
"anyOf": [
{
"type": "object",
"required": [
"maxBestDayProfitPct"
],
"properties": {
"maxBestDayProfitPct": {
"type": "number",
"maximum": 100,
"description": "Maximum share of the step's total profit the best single day may contribute, in PERCENT UNITS (40 = the best day may be at most 40% of total profit).",
"exclusiveMinimum": 0
}
},
"additionalProperties": {}
},
{
"type": "null"
}
],
"description": "Consistency rule - SIMULATED (engine v1), not just flagged: one outsized day effectively raises the target (total profit must reach best day / pct), and the simulated trader keeps trading - rationally stopping days early when that helps - until the best-day share complies (see flag 'consistency-stop-rule'). null or omitted = no consistency rule."
},
"minTradingDays": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0,
"description": "Minimum days with at least one trade before the step can be passed. Default 0."
},
"profitTargetPct": {
"type": "number",
"description": "Profit target in PERCENT UNITS of the initial account size (8 = 8%). Exactly one of profitTargetPct/profitTargetAmount.",
"exclusiveMinimum": 0
},
"profitTargetAmount": {
"type": "number",
"description": "Profit target as a fixed currency amount (alternative to profitTargetPct).",
"exclusiveMinimum": 0
}
},
"description": "One evaluation step. Each step starts on a fresh account at the initial balance.",
"additionalProperties": {}
},
"minItems": 1,
"description": "Evaluation steps in order. Passing the last step means funded."
},
"funded": {
"type": "object",
"required": [
"profitSplitPct",
"payoutFrequency"
],
"properties": {
"notes": {
"type": "string",
"description": "Free-text funded-stage details that are not simulated."
},
"maxLoss": {
"type": "object",
"required": [
"mode"
],
"properties": {
"pct": {
"type": "number",
"maximum": 100,
"description": "Max loss in PERCENT UNITS of the initial account size (10 = 10%). Exactly one of pct/amount.",
"exclusiveMinimum": 0
},
"mode": {
"enum": [
"static-initial",
"trailing-realized-eod",
"trailing-intraday-unrealized",
"trailing-locks-at-initial"
],
"type": "string",
"description": "How the max-loss floor behaves - the single most consequential rule difference between firms. 'static-initial': floor fixed at initial balance minus the limit; never moves (classic CFD two-step). 'trailing-realized-eod': floor ratchets up with end-of-day balance highs; intraday highs do not move it. 'trailing-intraday-unrealized': floor trails the peak unrealized equity intraday and never stops trailing (futures-style; the most-miscalculated rule in the industry: it cuts pass probability dramatically). 'trailing-locks-at-initial': trails intraday peak equity until the floor reaches the initial balance, then freezes (common futures variant). Locking is also composable: locksAtInitial adds the same lock to an EOD trail, and lockOffsetAmount shifts the lock level to initial balance + that amount (e.g. 100 models 'stops trailing $100 above the start')."
},
"amount": {
"type": "number",
"description": "Max loss as a fixed currency amount (alternative to pct).",
"exclusiveMinimum": 0
},
"locksAtInitial": {
"type": "boolean",
"description": "For trailing modes: once the trailing floor climbs up to the initial balance (plus lockOffsetAmount), it locks there and stops trailing. Default false. 'trailing-locks-at-initial' locks by definition; set this to add the same lock to 'trailing-realized-eod' (e.g. an EOD trail that stops at the starting balance)."
},
"lockOffsetAmount": {
"type": "number",
"minimum": 0,
"description": "Currency offset of the lock level: the floor locks at initial balance + this amount, modeling rules like 'the trailing threshold stops $100 above the start'. Default 0. Only meaningful when the rule locks (mode 'trailing-locks-at-initial' or locksAtInitial=true)."
}
},
"description": "Funded-account override of the max loss rule. Omit to inherit.",
"additionalProperties": {}
},
"dailyLoss": {
"anyOf": [
{
"type": "object",
"properties": {
"pct": {
"type": "number",
"maximum": 100,
"description": "Daily loss limit in PERCENT UNITS (5 = 5%); what it is a percent OF is set by limitBasis. Exactly one of pct/amount.",
"exclusiveMinimum": 0
},
"basis": {
"enum": [
"prior-day-balance",
"prior-day-equity"
],
"type": "string",
"description": "Anchor today's loss is measured from: prior day's closing balance or closing equity (they differ only with overnight positions). Default 'prior-day-balance'."
},
"amount": {
"type": "number",
"description": "Daily loss limit as a fixed currency amount (alternative to pct).",
"exclusiveMinimum": 0
},
"evaluation": {
"enum": [
"intraday",
"end-of-day"
],
"type": "string",
"description": "'intraday': fails the moment equity touches the daily floor. 'end-of-day': only the close is checked. Default 'intraday'."
},
"limitBasis": {
"enum": [
"initial-balance",
"anchor"
],
"type": "string",
"description": "What a percentage limit is a percent OF. 'initial-balance': a fixed currency allowance (always e.g. 5% of the starting account). 'anchor': recomputed daily from the day's anchor. Default 'initial-balance'."
},
"includesOpenPnl": {
"type": "boolean",
"description": "Whether floating (unrealized) P&L counts toward the daily loss, i.e. breach can happen intra-position. Default true."
}
},
"description": "Daily loss rule: the daily floor is anchor minus limit, reset at each trading-day boundary. Exactly one of pct/amount must be set.",
"additionalProperties": {}
},
{
"type": "null"
}
],
"description": "Funded-account override of the daily loss rule. Omit to inherit; null = none."
},
"payoutRules": {
"type": "object",
"properties": {
"bufferAmount": {
"type": "number",
"minimum": 0,
"description": "Profit buffer that must remain in the account; only profit above it is withdrawable. Default 0."
},
"minWinningDays": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0,
"description": "Winning days required in a payout window before a payout can be requested. Default 0."
},
"maxPayoutAmount": {
"type": "number",
"description": "Absolute currency cap per payout request. Omit for no fixed cap.",
"exclusiveMinimum": 0
},
"winningDayMinProfit": {
"type": "number",
"minimum": 0,
"description": "Minimum profit for a day to count as a winning day. Default 0 (any positive day)."
},
"maxPayoutPctOfProfit": {
"type": "number",
"maximum": 100,
"description": "Cap on each payout in PERCENT UNITS of accrued profit (50 = at most half the profit per request). Omit for no percentage cap.",
"exclusiveMinimum": 0
},
"consistencyMaxBestDayPct": {
"type": "number",
"maximum": 100,
"description": "Funded consistency gate in PERCENT UNITS: the best day may contribute at most this share of the payout window's profit. Evaluated per window (see flag 'funded-consistency-window-approximated').",
"exclusiveMinimum": 0
}
},
"description": "Payout gating - SIMULATED (engine v1), not just flagged: a payout happens only when these conditions are met, and on each eligible payout day the trader withdraws the maximum the rules allow (profit above the buffer, under the caps, never below the loss floor); balances and loss floors carry across payouts (see flag 'funded-withdrawal-model'). Omit for ungated payouts.",
"additionalProperties": {}
},
"profitSplitPct": {
"type": "number",
"maximum": 100,
"minimum": 0,
"description": "Trader's share of funded profits in PERCENT UNITS (80 = 80%)."
},
"payoutFrequency": {
"enum": [
"weekly",
"biweekly",
"monthly",
"on-demand"
],
"type": "string",
"description": "How often funded profits can be withdrawn."
},
"firstPayoutMinDays": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0,
"description": "Minimum days on the funded account before the first payout. Default 0."
}
},
"description": "Funded-stage terms used for the payout/EV simulation.",
"additionalProperties": {}
},
"maxLoss": {
"type": "object",
"required": [
"mode"
],
"properties": {
"pct": {
"type": "number",
"maximum": 100,
"description": "Max loss in PERCENT UNITS of the initial account size (10 = 10%). Exactly one of pct/amount.",
"exclusiveMinimum": 0
},
"mode": {
"enum": [
"static-initial",
"trailing-realized-eod",
"trailing-intraday-unrealized",
"trailing-locks-at-initial"
],
"type": "string",
"description": "How the max-loss floor behaves - the single most consequential rule difference between firms. 'static-initial': floor fixed at initial balance minus the limit; never moves (classic CFD two-step). 'trailing-realized-eod': floor ratchets up with end-of-day balance highs; intraday highs do not move it. 'trailing-intraday-unrealized': floor trails the peak unrealized equity intraday and never stops trailing (futures-style; the most-miscalculated rule in the industry: it cuts pass probability dramatically). 'trailing-locks-at-initial': trails intraday peak equity until the floor reaches the initial balance, then freezes (common futures variant). Locking is also composable: locksAtInitial adds the same lock to an EOD trail, and lockOffsetAmount shifts the lock level to initial balance + that amount (e.g. 100 models 'stops trailing $100 above the start')."
},
"amount": {
"type": "number",
"description": "Max loss as a fixed currency amount (alternative to pct).",
"exclusiveMinimum": 0
},
"locksAtInitial": {
"type": "boolean",
"description": "For trailing modes: once the trailing floor climbs up to the initial balance (plus lockOffsetAmount), it locks there and stops trailing. Default false. 'trailing-locks-at-initial' locks by definition; set this to add the same lock to 'trailing-realized-eod' (e.g. an EOD trail that stops at the starting balance)."
},
"lockOffsetAmount": {
"type": "number",
"minimum": 0,
"description": "Currency offset of the lock level: the floor locks at initial balance + this amount, modeling rules like 'the trailing threshold stops $100 above the start'. Default 0. Only meaningful when the rule locks (mode 'trailing-locks-at-initial' or locksAtInitial=true)."
}
},
"description": "Challenge-level max loss rule applied to every step unless a step overrides it. Required.",
"additionalProperties": {}
},
"sources": {
"type": "array",
"items": {
"type": "object",
"required": [
"url",
"lastVerified"
],
"properties": {
"url": {
"type": "string",
"description": "Public page documenting the rule."
},
"note": {
"type": "string"
},
"lastVerified": {
"type": "string",
"description": "ISO date the rules were last checked against that page."
}
},
"additionalProperties": {}
},
"description": "Public citations. Optional for inline specs; dataset entries always carry them."
},
"currency": {
"type": "string",
"description": "ISO currency code all amounts are denominated in. Default USD."
},
"dailyLoss": {
"anyOf": [
{
"type": "object",
"properties": {
"pct": {
"type": "number",
"maximum": 100,
"description": "Daily loss limit in PERCENT UNITS (5 = 5%); what it is a percent OF is set by limitBasis. Exactly one of pct/amount.",
"exclusiveMinimum": 0
},
"basis": {
"enum": [
"prior-day-balance",
"prior-day-equity"
],
"type": "string",
"description": "Anchor today's loss is measured from: prior day's closing balance or closing equity (they differ only with overnight positions). Default 'prior-day-balance'."
},
"amount": {
"type": "number",
"description": "Daily loss limit as a fixed currency amount (alternative to pct).",
"exclusiveMinimum": 0
},
"evaluation": {
"enum": [
"intraday",
"end-of-day"
],
"type": "string",
"description": "'intraday': fails the moment equity touches the daily floor. 'end-of-day': only the close is checked. Default 'intraday'."
},
"limitBasis": {
"enum": [
"initial-balance",
"anchor"
],
"type": "string",
"description": "What a percentage limit is a percent OF. 'initial-balance': a fixed currency allowance (always e.g. 5% of the starting account). 'anchor': recomputed daily from the day's anchor. Default 'initial-balance'."
},
"includesOpenPnl": {
"type": "boolean",
"description": "Whether floating (unrealized) P&L counts toward the daily loss, i.e. breach can happen intra-position. Default true."
}
},
"description": "Daily loss rule: the daily floor is anchor minus limit, reset at each trading-day boundary. Exactly one of pct/amount must be set.",
"additionalProperties": {}
},
{
"type": "null"
}
],
"description": "Challenge-level daily loss rule applied to every step unless a step overrides it. null = no daily loss rule. This field is required (pass null explicitly for none)."
},
"accountSize": {
"type": "number",
"description": "Initial account balance in account currency.",
"exclusiveMinimum": 0
},
"challengeId": {
"type": "string",
"minLength": 1,
"description": "Stable kebab-case id for this ruleset, e.g. '100k-2step'."
},
"constraints": {
"type": "object",
"description": "Informational trading constraints (maxLeverage, newsTrading, weekendHolding, ...). Recorded and flagged, never simulated.",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
},
"productType": {
"enum": [
"futures",
"cfd",
"equities"
],
"type": "string",
"description": "Instrument class the challenge is traded on: 'futures', 'cfd' (forex/CFD), or 'equities'."
},
"flagsNotSimulated": {
"type": "array",
"items": {
"type": "string"
},
"description": "Honesty channel: ids of rules this entry has that the engine does not simulate (e.g. 'scaling-plan', 'soft-daily-lockout'). Surfaced in every result's assumption flags. Consistency rules and payout gating do NOT belong here - the engine simulates them."
}
},
"description": "Inline challenge ruleset, for challenges not in the directory or for what-if rule edits. Mutually exclusive with firmId/challengeId. Identify the challenge EITHER by directory reference (firmId + challengeId, discovered via propfirms_list_simulatable; firmId accepts the directory id or the firm's name) OR by a full inline `spec` object - the exact shape propfirms_challenge_rules returns, so you can fetch a directory entry, change one rule, and re-simulate to model rule variations. Provide exactly one of the two forms; providing both or neither is an error. Directory references need network access; inline specs are fully offline.",
"additionalProperties": {}
},
"step": {
"type": "number",
"description": "Grid step, same units. Default 0.1. The sweep runs one full simulation per grid point, so (max - min) / step + 1 simulations in total - keep the grid coarse or paths low for a first pass.",
"exclusiveMinimum": 0
},
"paths": {
"type": "integer",
"maximum": 100000,
"minimum": 100,
"description": "Monte Carlo paths (independent simulated trader journeys). Default 10,000 (well under a second); capped at 100,000 per tool call. Confidence intervals shrink roughly with the square root of paths."
},
"firmId": {
"type": "string",
"minLength": 1,
"description": "Directory firm id or firm name (e.g. 'ftmo' or 'FTMO'); discover with propfirms_list_simulatable. Must be paired with challengeId. Mutually exclusive with `spec`."
},
"avgWinR": {
"type": "number",
"description": "Average winning trade in R-multiples, i.e. multiples of the amount risked per trade (1.5 = winners average 1.5x the risk).",
"exclusiveMinimum": 0
},
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
},
"winRate": {
"type": "number",
"maximum": 1,
"minimum": 0,
"description": "Probability a trade is a winner, as a FRACTION in [0, 1] (0.55 = 55% winners) - NOT percent units. The most impactful input: traders routinely overestimate it by a few points, which can flip EV negative, so prefer measured stats over self-reported ones."
},
"winStdR": {
"type": "number",
"minimum": 0,
"description": "Standard deviation of winner sizes in R (0 = every winner is exactly avgWinR). Default 0. Adding spread makes streak damage more realistic."
},
"avgLossR": {
"type": "number",
"description": "Average losing trade in R, as a POSITIVE number. Default 1 (losers lose exactly the risked amount, i.e. stops are honored). Raise above 1 to model slippage or blown stops.",
"exclusiveMinimum": 0
},
"lossStdR": {
"type": "number",
"minimum": 0,
"description": "Standard deviation of loser sizes in R (0 = every loser is exactly avgLossR). Default 0."
},
"riskMode": {
"enum": [
"percent-of-balance",
"percent-of-initial",
"fixed-amount"
],
"type": "string",
"description": "How riskValue is interpreted. 'percent-of-balance' (default): risk compounds with the current balance. 'percent-of-initial': constant currency risk derived from the initial account size - how most prop traders size, since loss limits are fixed in currency. 'fixed-amount': explicit currency risked per 1R."
},
"attemptCap": {
"type": "integer",
"maximum": 1000,
"minimum": 1,
"description": "Maximum challenge attempts per path before that path gives up. Default 25. Journey statistics (expected attempts/cost, P(funded)) are censored at this cap."
},
"challengeId": {
"type": "string",
"minLength": 1,
"description": "Directory challenge id; discover with propfirms_list_simulatable. Must be paired with firmId. Mutually exclusive with `spec`."
},
"tradesPerDay": {
"type": "number",
"description": "Average trades per simulated trading day. More trades per day means more ways to hit the daily loss limit within a single day.",
"exclusiveMinimum": 0
},
"simulateFunded": {
"type": "boolean",
"description": "Whether to simulate the funded stage (payouts, blowup risk) after passing. Default true - EV is only meaningful with it on; set false to study the evaluation alone."
},
"fundedHorizonDays": {
"type": "integer",
"maximum": 2000,
"minimum": 1,
"description": "Funded-stage horizon in trading days for the payout/EV simulation. Default 90 (about 4 calendar months). EV scales with this choice - state it when reporting EV."
},
"tradesPerDayModel": {
"enum": [
"fixed",
"poisson"
],
"type": "string",
"description": "'fixed' (default): the same count every day. 'poisson': daily count drawn Poisson(tradesPerDay); days can then have zero trades, which do not count as trading days."
}
}
}| challengeId | string | One challenge id. Omit to compute every simulatable challenge the firm has. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"firmId",
"context"
],
"properties": {
"firmId": {
"type": "string",
"minLength": 1,
"description": "Directory firm id (propfirmId, e.g. 'ftmo') or firm name — from propfirms_list_simulatable."
},
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
},
"challengeId": {
"type": "string",
"minLength": 1,
"description": "One challenge id. Omit to compute every simulatable challenge the firm has."
}
}
}| include | array | Extra payloads to nest on each firm (only children matching the filters are returned) |
| offerId | array | Public offer ids |
| currency | array | Account currencies, e.g. ['usd', 'eur'] |
| interval | array | Challenge fee intervals, e.g. 'one-time', 'monthly' |
| priceMax | number | Maximum challenge fee (inclusive) |
| priceMin | number | Minimum challenge fee (inclusive) |
| stepsMax | integer | Maximum step count (ignored when steps is set) |
| stepsMin | integer | Minimum step count (ignored when steps is set) |
| direction | string | Sort direction; each sort key has a sensible default |
| offerText | string | Case-insensitive search over promo code and offer descriptions |
| pageIndex | integer | 0-based page index (default 0) |
| promoCode | string | Case-insensitive substring of the promo code |
| isFeatured | boolean | Only featured offers when true |
| maxLossMax | number | Upper bound on the overall-loss limit magnitude |
| propfirmId | array | Public firm slugs, e.g. ['ftmo'] |
| autoTrading | boolean | Whether automated trading (EAs/bots) is allowed |
| availableIn | array | Country names the firm must NOT restrict, e.g. ['United States'] |
| challengeId | array | Public challenge ids |
| copyTrading | boolean | Whether copy trading is allowed |
| countryIso2 | array | ISO-2 headquarters countries, e.g. ['GB', 'US'] |
| discountMax | number | Maximum discount value |
| discountMin | number | Minimum discount value |
| maxLossMode | array | Drawdown modes; challenges without a captured mode never match |
| newsTrading | boolean | Whether news trading is allowed |
| dailyLossMax | number | Upper bound on the daily-loss limit magnitude (smaller = stricter) |
| pageQuantity | integer | Page size (default 50, max 100) |
| productTypes | array | Product types the firm must offer at least one of, e.g. 'CFD', 'Futures' |
| challengeName | string | Case-insensitive substring of the challenge name |
| payoutMethods | array | Payout methods the firm must offer at least one of, e.g. 'Bank Transfer', 'Crypto' |
| accountSizeMax | number | Maximum account size (inclusive) |
| accountSizeMin | number | Minimum account size (inclusive) |
| hasActiveOffer | boolean | When true, the firm must currently have a live (active, unexpired) offer |
| includeExpired | boolean | When true, ended offers are not hidden (default false) |
| maxLeverageMin | number | Minimum max leverage |
| maxYearFounded | integer | Inclusive maximum year founded |
| minYearFounded | integer | Inclusive minimum year founded |
| paymentMethods | array | Payment methods the firm must accept at least one of, e.g. 'Crypto', 'PayPal' |
| profitSplitMin | number | Minimum trader profit-split percent |
| weekendHolding | boolean | Whether holding over the weekend is allowed |
| includeInactive | boolean | When true, inactive offers are not hidden (default false) |
| isFeeRefundable | boolean | Whether the challenge fee is refundable |
| overnightHolding | boolean | Whether holding overnight is allowed |
| stoplossRequired | boolean | Whether a stop loss is required |
| tradingPlatforms | array | Platforms the firm must offer at least one of, e.g. 'MT5', 'cTrader', 'TradingView' |
| discountIsPercent | boolean | true for percent discounts, false for absolute amounts |
| minTradingDaysMax | number | Maximum required minimum trading days (finds less-strict challenges) |
| tradedMarketTypes | array | Markets the firm must offer at least one of, e.g. 'forex', 'indices', 'commodities' |
| isPreferredPartner | boolean | Only LuxAlgo preferred-partner firms when true |
| minTrustPilotCount | number | Minimum Trustpilot review count |
| minTrustPilotScore | number | Minimum Trustpilot score |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"context"
],
"properties": {
"sort": {
"enum": [
"name",
"yearFounded",
"reviewsTrustPilotScore",
"reviewsTrustPilotCount"
],
"type": "string",
"description": "Sort key (default name)"
},
"text": {
"type": "string",
"description": "Case-insensitive search over firm name and slug, e.g. 'ftmo'"
},
"steps": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991,
"description": "Exact evaluation step count (1 = instant/funded, 2 = two-step, …)"
},
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
},
"include": {
"type": "array",
"items": {
"enum": [
"challenges",
"offers",
"overview"
],
"type": "string"
},
"description": "Extra payloads to nest on each firm (only children matching the filters are returned)"
},
"offerId": {
"type": "array",
"items": {
"type": "string"
},
"description": "Public offer ids"
},
"currency": {
"type": "array",
"items": {
"type": "string"
},
"description": "Account currencies, e.g. ['usd', 'eur']"
},
"interval": {
"type": "array",
"items": {
"type": "string"
},
"description": "Challenge fee intervals, e.g. 'one-time', 'monthly'"
},
"priceMax": {
"type": "number",
"description": "Maximum challenge fee (inclusive)"
},
"priceMin": {
"type": "number",
"description": "Minimum challenge fee (inclusive)"
},
"stepsMax": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991,
"description": "Maximum step count (ignored when steps is set)"
},
"stepsMin": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991,
"description": "Minimum step count (ignored when steps is set)"
},
"direction": {
"enum": [
"asc",
"desc"
],
"type": "string",
"description": "Sort direction; each sort key has a sensible default"
},
"offerText": {
"type": "string",
"description": "Case-insensitive search over promo code and offer descriptions"
},
"pageIndex": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0,
"description": "0-based page index (default 0)"
},
"promoCode": {
"type": "string",
"description": "Case-insensitive substring of the promo code"
},
"isFeatured": {
"type": "boolean",
"description": "Only featured offers when true"
},
"maxLossMax": {
"type": "number",
"description": "Upper bound on the overall-loss limit magnitude"
},
"propfirmId": {
"type": "array",
"items": {
"type": "string"
},
"description": "Public firm slugs, e.g. ['ftmo']"
},
"autoTrading": {
"type": "boolean",
"description": "Whether automated trading (EAs/bots) is allowed"
},
"availableIn": {
"type": "array",
"items": {
"type": "string"
},
"description": "Country names the firm must NOT restrict, e.g. ['United States']"
},
"challengeId": {
"type": "array",
"items": {
"type": "string"
},
"description": "Public challenge ids"
},
"copyTrading": {
"type": "boolean",
"description": "Whether copy trading is allowed"
},
"countryIso2": {
"type": "array",
"items": {
"type": "string"
},
"description": "ISO-2 headquarters countries, e.g. ['GB', 'US']"
},
"discountMax": {
"type": "number",
"description": "Maximum discount value"
},
"discountMin": {
"type": "number",
"description": "Minimum discount value"
},
"maxLossMode": {
"type": "array",
"items": {
"enum": [
"static-initial",
"trailing-realized-eod",
"trailing-intraday-unrealized"
],
"type": "string"
},
"description": "Drawdown modes; challenges without a captured mode never match"
},
"newsTrading": {
"type": "boolean",
"description": "Whether news trading is allowed"
},
"dailyLossMax": {
"type": "number",
"description": "Upper bound on the daily-loss limit magnitude (smaller = stricter)"
},
"pageQuantity": {
"type": "integer",
"maximum": 100,
"minimum": 1,
"description": "Page size (default 50, max 100)"
},
"productTypes": {
"type": "array",
"items": {
"type": "string"
},
"description": "Product types the firm must offer at least one of, e.g. 'CFD', 'Futures'"
},
"challengeName": {
"type": "string",
"description": "Case-insensitive substring of the challenge name"
},
"payoutMethods": {
"type": "array",
"items": {
"type": "string"
},
"description": "Payout methods the firm must offer at least one of, e.g. 'Bank Transfer', 'Crypto'"
},
"accountSizeMax": {
"type": "number",
"description": "Maximum account size (inclusive)"
},
"accountSizeMin": {
"type": "number",
"description": "Minimum account size (inclusive)"
},
"hasActiveOffer": {
"type": "boolean",
"description": "When true, the firm must currently have a live (active, unexpired) offer"
},
"includeExpired": {
"type": "boolean",
"description": "When true, ended offers are not hidden (default false)"
},
"maxLeverageMin": {
"type": "number",
"description": "Minimum max leverage"
},
"maxYearFounded": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991,
"description": "Inclusive maximum year founded"
},
"minYearFounded": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991,
"description": "Inclusive minimum year founded"
},
"paymentMethods": {
"type": "array",
"items": {
"type": "string"
},
"description": "Payment methods the firm must accept at least one of, e.g. 'Crypto', 'PayPal'"
},
"profitSplitMin": {
"type": "number",
"description": "Minimum trader profit-split percent"
},
"weekendHolding": {
"type": "boolean",
"description": "Whether holding over the weekend is allowed"
},
"includeInactive": {
"type": "boolean",
"description": "When true, inactive offers are not hidden (default false)"
},
"isFeeRefundable": {
"type": "boolean",
"description": "Whether the challenge fee is refundable"
},
"overnightHolding": {
"type": "boolean",
"description": "Whether holding overnight is allowed"
},
"stoplossRequired": {
"type": "boolean",
"description": "Whether a stop loss is required"
},
"tradingPlatforms": {
"type": "array",
"items": {
"type": "string"
},
"description": "Platforms the firm must offer at least one of, e.g. 'MT5', 'cTrader', 'TradingView'"
},
"discountIsPercent": {
"type": "boolean",
"description": "true for percent discounts, false for absolute amounts"
},
"minTradingDaysMax": {
"type": "number",
"description": "Maximum required minimum trading days (finds less-strict challenges)"
},
"tradedMarketTypes": {
"type": "array",
"items": {
"type": "string"
},
"description": "Markets the firm must offer at least one of, e.g. 'forex', 'indices', 'commodities'"
},
"isPreferredPartner": {
"type": "boolean",
"description": "Only LuxAlgo preferred-partner firms when true"
},
"minTrustPilotCount": {
"type": "number",
"description": "Minimum Trustpilot review count"
},
"minTrustPilotScore": {
"type": "number",
"description": "Minimum Trustpilot score"
}
}
}| include | array | Pass ['offers'] to attach live offers that apply to each challenge |
| interval | array | Challenge fee intervals, e.g. 'one-time', 'monthly' |
| priceMax | number | Maximum challenge fee (inclusive) |
| priceMin | number | Minimum challenge fee (inclusive) |
| stepsMax | integer | Maximum step count (ignored when steps is set) |
| stepsMin | integer | Minimum step count (ignored when steps is set) |
| direction | string | Sort direction; each sort key has a sensible default |
| pageIndex | integer | 0-based page index (default 0) |
| maxLossMax | number | Upper bound on the overall-loss limit magnitude |
| propfirmId | array | Public firm slugs, e.g. ['ftmo'] |
| autoTrading | boolean | Whether automated trading (EAs/bots) is allowed |
| availableIn | array | Country names the firm must NOT restrict, e.g. ['United States'] |
| challengeId | array | Public challenge ids |
| copyTrading | boolean | Whether copy trading is allowed |
| maxLossMode | array | Drawdown modes; challenges without a captured mode never match |
| newsTrading | boolean | Whether news trading is allowed |
| dailyLossMax | number | Upper bound on the daily-loss limit magnitude (smaller = stricter) |
| pageQuantity | integer | Page size (default 50, max 100) |
| productTypes | array | Product types the firm must offer at least one of, e.g. 'CFD', 'Futures' |
| challengeName | string | Case-insensitive substring of the challenge name |
| accountSizeMax | number | Maximum account size (inclusive) |
| accountSizeMin | number | Minimum account size (inclusive) |
| maxLeverageMin | number | Minimum max leverage |
| profitSplitMin | number | Minimum trader profit-split percent |
| weekendHolding | boolean | Whether holding over the weekend is allowed |
| isFeeRefundable | boolean | Whether the challenge fee is refundable |
| overnightHolding | boolean | Whether holding overnight is allowed |
| stoplossRequired | boolean | Whether a stop loss is required |
| tradingPlatforms | array | Platforms the firm must offer at least one of, e.g. 'MT5', 'cTrader', 'TradingView' |
| minTradingDaysMax | number | Maximum required minimum trading days (finds less-strict challenges) |
| tradedMarketTypes | array | Markets the firm must offer at least one of, e.g. 'forex', 'indices', 'commodities' |
| isPreferredPartner | boolean | Only LuxAlgo preferred-partner firms when true |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"context"
],
"properties": {
"sort": {
"enum": [
"challengeName",
"accountSize",
"price",
"steps",
"profitSplitPercent"
],
"type": "string",
"description": "Sort key (default accountSize descending)"
},
"text": {
"type": "string",
"description": "Case-insensitive search over challenge name and firm name/slug"
},
"steps": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991,
"description": "Exact evaluation step count (1 = instant/funded, 2 = two-step, …)"
},
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
},
"include": {
"type": "array",
"items": {
"enum": [
"offers"
],
"type": "string"
},
"description": "Pass ['offers'] to attach live offers that apply to each challenge"
},
"interval": {
"type": "array",
"items": {
"type": "string"
},
"description": "Challenge fee intervals, e.g. 'one-time', 'monthly'"
},
"priceMax": {
"type": "number",
"description": "Maximum challenge fee (inclusive)"
},
"priceMin": {
"type": "number",
"description": "Minimum challenge fee (inclusive)"
},
"stepsMax": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991,
"description": "Maximum step count (ignored when steps is set)"
},
"stepsMin": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991,
"description": "Minimum step count (ignored when steps is set)"
},
"direction": {
"enum": [
"asc",
"desc"
],
"type": "string",
"description": "Sort direction; each sort key has a sensible default"
},
"pageIndex": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0,
"description": "0-based page index (default 0)"
},
"maxLossMax": {
"type": "number",
"description": "Upper bound on the overall-loss limit magnitude"
},
"propfirmId": {
"type": "array",
"items": {
"type": "string"
},
"description": "Public firm slugs, e.g. ['ftmo']"
},
"autoTrading": {
"type": "boolean",
"description": "Whether automated trading (EAs/bots) is allowed"
},
"availableIn": {
"type": "array",
"items": {
"type": "string"
},
"description": "Country names the firm must NOT restrict, e.g. ['United States']"
},
"challengeId": {
"type": "array",
"items": {
"type": "string"
},
"description": "Public challenge ids"
},
"copyTrading": {
"type": "boolean",
"description": "Whether copy trading is allowed"
},
"maxLossMode": {
"type": "array",
"items": {
"enum": [
"static-initial",
"trailing-realized-eod",
"trailing-intraday-unrealized"
],
"type": "string"
},
"description": "Drawdown modes; challenges without a captured mode never match"
},
"newsTrading": {
"type": "boolean",
"description": "Whether news trading is allowed"
},
"dailyLossMax": {
"type": "number",
"description": "Upper bound on the daily-loss limit magnitude (smaller = stricter)"
},
"pageQuantity": {
"type": "integer",
"maximum": 100,
"minimum": 1,
"description": "Page size (default 50, max 100)"
},
"productTypes": {
"type": "array",
"items": {
"type": "string"
},
"description": "Product types the firm must offer at least one of, e.g. 'CFD', 'Futures'"
},
"challengeName": {
"type": "string",
"description": "Case-insensitive substring of the challenge name"
},
"accountSizeMax": {
"type": "number",
"description": "Maximum account size (inclusive)"
},
"accountSizeMin": {
"type": "number",
"description": "Minimum account size (inclusive)"
},
"maxLeverageMin": {
"type": "number",
"description": "Minimum max leverage"
},
"profitSplitMin": {
"type": "number",
"description": "Minimum trader profit-split percent"
},
"weekendHolding": {
"type": "boolean",
"description": "Whether holding over the weekend is allowed"
},
"isFeeRefundable": {
"type": "boolean",
"description": "Whether the challenge fee is refundable"
},
"overnightHolding": {
"type": "boolean",
"description": "Whether holding overnight is allowed"
},
"stoplossRequired": {
"type": "boolean",
"description": "Whether a stop loss is required"
},
"tradingPlatforms": {
"type": "array",
"items": {
"type": "string"
},
"description": "Platforms the firm must offer at least one of, e.g. 'MT5', 'cTrader', 'TradingView'"
},
"minTradingDaysMax": {
"type": "number",
"description": "Maximum required minimum trading days (finds less-strict challenges)"
},
"tradedMarketTypes": {
"type": "array",
"items": {
"type": "string"
},
"description": "Markets the firm must offer at least one of, e.g. 'forex', 'indices', 'commodities'"
},
"isPreferredPartner": {
"type": "boolean",
"description": "Only LuxAlgo preferred-partner firms when true"
}
}
}| string |
| Sort direction; each sort key has a sensible default |
| offerText | string | Case-insensitive search over promo code and offer descriptions |
| pageIndex | integer | 0-based page index (default 0) |
| promoCode | string | Case-insensitive substring of the promo code |
| isFeatured | boolean | Only featured offers when true |
| propfirmId | array | Public firm slugs, e.g. ['ftmo'] |
| challengeId | array | Public challenge ids; an offer matches when it applies to at least one (all-challenges offers match that firm's challenges) |
| discountMax | number | Maximum discount value |
| discountMin | number | Minimum discount value |
| pageQuantity | integer | Page size (default 50, max 100) |
| includeExpired | boolean | When true, ended offers are not hidden (default false) |
| includeInactive | boolean | When true, inactive offers are not hidden (default false) |
| discountIsPercent | boolean | true for percent discounts, false for absolute amounts |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"context"
],
"properties": {
"sort": {
"enum": [
"discountValue",
"endsAt",
"promoCode"
],
"type": "string",
"description": "Sort key (default: featured first, then discount)"
},
"text": {
"type": "string",
"description": "Case-insensitive search over promo code, descriptions, and firm name/slug"
},
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
},
"offerId": {
"type": "array",
"items": {
"type": "string"
},
"description": "Public offer ids"
},
"isActive": {
"type": "boolean",
"description": "Defaults to live offers only; pass false to look at inactive offers"
},
"direction": {
"enum": [
"asc",
"desc"
],
"type": "string",
"description": "Sort direction; each sort key has a sensible default"
},
"offerText": {
"type": "string",
"description": "Case-insensitive search over promo code and offer descriptions"
},
"pageIndex": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0,
"description": "0-based page index (default 0)"
},
"promoCode": {
"type": "string",
"description": "Case-insensitive substring of the promo code"
},
"isFeatured": {
"type": "boolean",
"description": "Only featured offers when true"
},
"propfirmId": {
"type": "array",
"items": {
"type": "string"
},
"description": "Public firm slugs, e.g. ['ftmo']"
},
"challengeId": {
"type": "array",
"items": {
"type": "string"
},
"description": "Public challenge ids; an offer matches when it applies to at least one (all-challenges offers match that firm's challenges)"
},
"discountMax": {
"type": "number",
"description": "Maximum discount value"
},
"discountMin": {
"type": "number",
"description": "Minimum discount value"
},
"pageQuantity": {
"type": "integer",
"maximum": 100,
"minimum": 1,
"description": "Page size (default 50, max 100)"
},
"includeExpired": {
"type": "boolean",
"description": "When true, ended offers are not hidden (default false)"
},
"includeInactive": {
"type": "boolean",
"description": "When true, inactive offers are not hidden (default false)"
},
"discountIsPercent": {
"type": "boolean",
"description": "true for percent discounts, false for absolute amounts"
}
}
}| Argument | Type | Description |
|---|---|---|
| seed | any | RNG seed (integer or string). Default 42. Same inputs + seed reproduce byte-identical results - include the seed when reporting so users can reproduce the numbers. |
| spec | object | Inline challenge ruleset, for challenges not in the directory or for what-if rule edits. Mutually exclusive with firmId/challengeId. Identify the challenge EITHER by directory reference (firmId + challengeId, discovered via propfirms_list_simulatable; firmId accepts the directory id or the firm's name) OR by a full inline `spec` object - the exact shape propfirms_challenge_rules returns, so you can fetch a directory entry, change one rule, and re-simulate to model rule variations. Provide exactly one of the two forms; providing both or neither is an error. Directory references need network access; inline specs are fully offline. |
| paths | integer | Monte Carlo paths (independent simulated trader journeys). Default 10,000 (well under a second); capped at 100,000 per tool call. Confidence intervals shrink roughly with the square root of paths. |
| firmId | string | Directory firm id or firm name (e.g. 'ftmo' or 'FTMO'); discover with propfirms_list_simulatable. Must be paired with challengeId. Mutually exclusive with `spec`. |
| avgWinR* | number | Average winning trade in R-multiples, i.e. multiples of the amount risked per trade (1.5 = winners average 1.5x the risk). |
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
| winRate* | number | Probability a trade is a winner, as a FRACTION in [0, 1] (0.55 = 55% winners) - NOT percent units. The most impactful input: traders routinely overestimate it by a few points, which can flip EV negative, so prefer measured stats over self-reported ones. |
| winStdR | number | Standard deviation of winner sizes in R (0 = every winner is exactly avgWinR). Default 0. Adding spread makes streak damage more realistic. |
| avgLossR | number | Average losing trade in R, as a POSITIVE number. Default 1 (losers lose exactly the risked amount, i.e. stops are honored). Raise above 1 to model slippage or blown stops. |
| lossStdR | number | Standard deviation of loser sizes in R (0 = every loser is exactly avgLossR). Default 0. |
| riskMode | string | How riskValue is interpreted. 'percent-of-balance' (default): risk compounds with the current balance. 'percent-of-initial': constant currency risk derived from the initial account size - how most prop traders size, since loss limits are fixed in currency. 'fixed-amount': explicit currency risked per 1R. |
| riskValue* | number | Risk per trade - the value of 1R. PERCENT UNITS for percent modes (0.5 = 0.5% risked per trade; a typical prop range is 0.25-2), or a currency amount for 'fixed-amount'. NOT a fraction. |
| attemptCap | integer | Maximum challenge attempts per path before that path gives up. Default 25. Journey statistics (expected attempts/cost, P(funded)) are censored at this cap. |
| challengeId | string | Directory challenge id; discover with propfirms_list_simulatable. Must be paired with firmId. Mutually exclusive with `spec`. |
| tradesPerDay* | number | Average trades per simulated trading day. More trades per day means more ways to hit the daily loss limit within a single day. |
| simulateFunded | boolean | Whether to simulate the funded stage (payouts, blowup risk) after passing. Default true - EV is only meaningful with it on; set false to study the evaluation alone. |
| fundedHorizonDays | integer | Funded-stage horizon in trading days for the payout/EV simulation. Default 90 (about 4 calendar months). EV scales with this choice - state it when reporting EV. |
| includeHistograms | boolean | Include histogram arrays (attempts, cost, net, drawdown) in the result. Default FALSE for this tool to keep responses compact; summary quantiles (p05...p95) are always included. |
| tradesPerDayModel | string | 'fixed' (default): the same count every day. 'poisson': daily count drawn Poisson(tradesPerDay); days can then have zero trades, which do not count as trading days. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"winRate",
"avgWinR",
"tradesPerDay",
"riskValue",
"context"
],
"properties": {
"seed": {
"anyOf": [
{
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991
},
{
"type": "string"
}
],
"description": "RNG seed (integer or string). Default 42. Same inputs + seed reproduce byte-identical results - include the seed when reporting so users can reproduce the numbers."
},
"spec": {
"type": "object",
"required": [
"challengeId",
"name",
"accountSize",
"steps",
"dailyLoss",
"maxLoss",
"fees",
"funded"
],
"properties": {
"fees": {
"type": "object",
"required": [
"price"
],
"properties": {
"price": {
"type": "number",
"minimum": 0,
"description": "Challenge price in account currency. Under 'monthly' billing: price per month."
},
"billing": {
"enum": [
"one-time",
"monthly"
],
"type": "string",
"description": "'one-time' (default): the price buys one attempt; failed attempts are re-bought or reset. 'monthly': recurring subscription while evaluating (common for futures firms)."
},
"resetFee": {
"anyOf": [
{
"type": "number",
"minimum": 0
},
{
"type": "null"
}
],
"description": "Discounted fee to reset a failed attempt. null (default) = no reset offer: a failed one-time attempt costs full price again; a failed monthly attempt rides on the subscription."
},
"activationFee": {
"type": "number",
"minimum": 0,
"description": "One-time fee charged when the funded account is activated. Default 0."
},
"refundableOnPass": {
"type": "boolean",
"description": "Whether the one-time challenge fee is refunded once funded (credited back in cost/EV). Default false."
}
},
"description": "Fees - everything that goes into expected total cost.",
"additionalProperties": {}
},
"name": {
"type": "string",
"minLength": 1,
"description": "Display name, e.g. '100K 2-Step'."
},
"steps": {
"type": "array",
"items": {
"type": "object",
"properties": {
"maxDays": {
"anyOf": [
{
"type": "integer",
"maximum": 9007199254740991,
"exclusiveMinimum": 0
},
{
"type": "null"
}
],
"description": "Trading-day limit for the step; null (the default) = unlimited time."
},
"maxLoss": {
"type": "object",
"required": [
"mode"
],
"properties": {
"pct": {
"type": "number",
"maximum": 100,
"description": "Max loss in PERCENT UNITS of the initial account size (10 = 10%). Exactly one of pct/amount.",
"exclusiveMinimum": 0
},
"mode": {
"enum": [
"static-initial",
"trailing-realized-eod",
"trailing-intraday-unrealized",
"trailing-locks-at-initial"
],
"type": "string",
"description": "How the max-loss floor behaves - the single most consequential rule difference between firms. 'static-initial': floor fixed at initial balance minus the limit; never moves (classic CFD two-step). 'trailing-realized-eod': floor ratchets up with end-of-day balance highs; intraday highs do not move it. 'trailing-intraday-unrealized': floor trails the peak unrealized equity intraday and never stops trailing (futures-style; the most-miscalculated rule in the industry: it cuts pass probability dramatically). 'trailing-locks-at-initial': trails intraday peak equity until the floor reaches the initial balance, then freezes (common futures variant). Locking is also composable: locksAtInitial adds the same lock to an EOD trail, and lockOffsetAmount shifts the lock level to initial balance + that amount (e.g. 100 models 'stops trailing $100 above the start')."
},
"amount": {
"type": "number",
"description": "Max loss as a fixed currency amount (alternative to pct).",
"exclusiveMinimum": 0
},
"locksAtInitial": {
"type": "boolean",
"description": "For trailing modes: once the trailing floor climbs up to the initial balance (plus lockOffsetAmount), it locks there and stops trailing. Default false. 'trailing-locks-at-initial' locks by definition; set this to add the same lock to 'trailing-realized-eod' (e.g. an EOD trail that stops at the starting balance)."
},
"lockOffsetAmount": {
"type": "number",
"minimum": 0,
"description": "Currency offset of the lock level: the floor locks at initial balance + this amount, modeling rules like 'the trailing threshold stops $100 above the start'. Default 0. Only meaningful when the rule locks (mode 'trailing-locks-at-initial' or locksAtInitial=true)."
}
},
"description": "Per-step override of the challenge-level max loss rule. Omit to inherit.",
"additionalProperties": {}
},
"dailyLoss": {
"anyOf": [
{
"type": "object",
"properties": {
"pct": {
"type": "number",
"maximum": 100,
"description": "Daily loss limit in PERCENT UNITS (5 = 5%); what it is a percent OF is set by limitBasis. Exactly one of pct/amount.",
"exclusiveMinimum": 0
},
"basis": {
"enum": [
"prior-day-balance",
"prior-day-equity"
],
"type": "string",
"description": "Anchor today's loss is measured from: prior day's closing balance or closing equity (they differ only with overnight positions). Default 'prior-day-balance'."
},
"amount": {
"type": "number",
"description": "Daily loss limit as a fixed currency amount (alternative to pct).",
"exclusiveMinimum": 0
},
"evaluation": {
"enum": [
"intraday",
"end-of-day"
],
"type": "string",
"description": "'intraday': fails the moment equity touches the daily floor. 'end-of-day': only the close is checked. Default 'intraday'."
},
"limitBasis": {
"enum": [
"initial-balance",
"anchor"
],
"type": "string",
"description": "What a percentage limit is a percent OF. 'initial-balance': a fixed currency allowance (always e.g. 5% of the starting account). 'anchor': recomputed daily from the day's anchor. Default 'initial-balance'."
},
"includesOpenPnl": {
"type": "boolean",
"description": "Whether floating (unrealized) P&L counts toward the daily loss, i.e. breach can happen intra-position. Default true."
}
},
"description": "Daily loss rule: the daily floor is anchor minus limit, reset at each trading-day boundary. Exactly one of pct/amount must be set.",
"additionalProperties": {}
},
{
"type": "null"
}
],
"description": "Per-step override of the challenge-level daily loss rule. Omit to inherit; null = no daily loss rule in this step."
},
"consistency": {
"anyOf": [
{
"type": "object",
"required": [
"maxBestDayProfitPct"
],
"properties": {
"maxBestDayProfitPct": {
"type": "number",
"maximum": 100,
"description": "Maximum share of the step's total profit the best single day may contribute, in PERCENT UNITS (40 = the best day may be at most 40% of total profit).",
"exclusiveMinimum": 0
}
},
"additionalProperties": {}
},
{
"type": "null"
}
],
"description": "Consistency rule - SIMULATED (engine v1), not just flagged: one outsized day effectively raises the target (total profit must reach best day / pct), and the simulated trader keeps trading - rationally stopping days early when that helps - until the best-day share complies (see flag 'consistency-stop-rule'). null or omitted = no consistency rule."
},
"minTradingDays": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0,
"description": "Minimum days with at least one trade before the step can be passed. Default 0."
},
"profitTargetPct": {
"type": "number",
"description": "Profit target in PERCENT UNITS of the initial account size (8 = 8%). Exactly one of profitTargetPct/profitTargetAmount.",
"exclusiveMinimum": 0
},
"profitTargetAmount": {
"type": "number",
"description": "Profit target as a fixed currency amount (alternative to profitTargetPct).",
"exclusiveMinimum": 0
}
},
"description": "One evaluation step. Each step starts on a fresh account at the initial balance.",
"additionalProperties": {}
},
"minItems": 1,
"description": "Evaluation steps in order. Passing the last step means funded."
},
"funded": {
"type": "object",
"required": [
"profitSplitPct",
"payoutFrequency"
],
"properties": {
"notes": {
"type": "string",
"description": "Free-text funded-stage details that are not simulated."
},
"maxLoss": {
"type": "object",
"required": [
"mode"
],
"properties": {
"pct": {
"type": "number",
"maximum": 100,
"description": "Max loss in PERCENT UNITS of the initial account size (10 = 10%). Exactly one of pct/amount.",
"exclusiveMinimum": 0
},
"mode": {
"enum": [
"static-initial",
"trailing-realized-eod",
"trailing-intraday-unrealized",
"trailing-locks-at-initial"
],
"type": "string",
"description": "How the max-loss floor behaves - the single most consequential rule difference between firms. 'static-initial': floor fixed at initial balance minus the limit; never moves (classic CFD two-step). 'trailing-realized-eod': floor ratchets up with end-of-day balance highs; intraday highs do not move it. 'trailing-intraday-unrealized': floor trails the peak unrealized equity intraday and never stops trailing (futures-style; the most-miscalculated rule in the industry: it cuts pass probability dramatically). 'trailing-locks-at-initial': trails intraday peak equity until the floor reaches the initial balance, then freezes (common futures variant). Locking is also composable: locksAtInitial adds the same lock to an EOD trail, and lockOffsetAmount shifts the lock level to initial balance + that amount (e.g. 100 models 'stops trailing $100 above the start')."
},
"amount": {
"type": "number",
"description": "Max loss as a fixed currency amount (alternative to pct).",
"exclusiveMinimum": 0
},
"locksAtInitial": {
"type": "boolean",
"description": "For trailing modes: once the trailing floor climbs up to the initial balance (plus lockOffsetAmount), it locks there and stops trailing. Default false. 'trailing-locks-at-initial' locks by definition; set this to add the same lock to 'trailing-realized-eod' (e.g. an EOD trail that stops at the starting balance)."
},
"lockOffsetAmount": {
"type": "number",
"minimum": 0,
"description": "Currency offset of the lock level: the floor locks at initial balance + this amount, modeling rules like 'the trailing threshold stops $100 above the start'. Default 0. Only meaningful when the rule locks (mode 'trailing-locks-at-initial' or locksAtInitial=true)."
}
},
"description": "Funded-account override of the max loss rule. Omit to inherit.",
"additionalProperties": {}
},
"dailyLoss": {
"anyOf": [
{
"type": "object",
"properties": {
"pct": {
"type": "number",
"maximum": 100,
"description": "Daily loss limit in PERCENT UNITS (5 = 5%); what it is a percent OF is set by limitBasis. Exactly one of pct/amount.",
"exclusiveMinimum": 0
},
"basis": {
"enum": [
"prior-day-balance",
"prior-day-equity"
],
"type": "string",
"description": "Anchor today's loss is measured from: prior day's closing balance or closing equity (they differ only with overnight positions). Default 'prior-day-balance'."
},
"amount": {
"type": "number",
"description": "Daily loss limit as a fixed currency amount (alternative to pct).",
"exclusiveMinimum": 0
},
"evaluation": {
"enum": [
"intraday",
"end-of-day"
],
"type": "string",
"description": "'intraday': fails the moment equity touches the daily floor. 'end-of-day': only the close is checked. Default 'intraday'."
},
"limitBasis": {
"enum": [
"initial-balance",
"anchor"
],
"type": "string",
"description": "What a percentage limit is a percent OF. 'initial-balance': a fixed currency allowance (always e.g. 5% of the starting account). 'anchor': recomputed daily from the day's anchor. Default 'initial-balance'."
},
"includesOpenPnl": {
"type": "boolean",
"description": "Whether floating (unrealized) P&L counts toward the daily loss, i.e. breach can happen intra-position. Default true."
}
},
"description": "Daily loss rule: the daily floor is anchor minus limit, reset at each trading-day boundary. Exactly one of pct/amount must be set.",
"additionalProperties": {}
},
{
"type": "null"
}
],
"description": "Funded-account override of the daily loss rule. Omit to inherit; null = none."
},
"payoutRules": {
"type": "object",
"properties": {
"bufferAmount": {
"type": "number",
"minimum": 0,
"description": "Profit buffer that must remain in the account; only profit above it is withdrawable. Default 0."
},
"minWinningDays": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0,
"description": "Winning days required in a payout window before a payout can be requested. Default 0."
},
"maxPayoutAmount": {
"type": "number",
"description": "Absolute currency cap per payout request. Omit for no fixed cap.",
"exclusiveMinimum": 0
},
"winningDayMinProfit": {
"type": "number",
"minimum": 0,
"description": "Minimum profit for a day to count as a winning day. Default 0 (any positive day)."
},
"maxPayoutPctOfProfit": {
"type": "number",
"maximum": 100,
"description": "Cap on each payout in PERCENT UNITS of accrued profit (50 = at most half the profit per request). Omit for no percentage cap.",
"exclusiveMinimum": 0
},
"consistencyMaxBestDayPct": {
"type": "number",
"maximum": 100,
"description": "Funded consistency gate in PERCENT UNITS: the best day may contribute at most this share of the payout window's profit. Evaluated per window (see flag 'funded-consistency-window-approximated').",
"exclusiveMinimum": 0
}
},
"description": "Payout gating - SIMULATED (engine v1), not just flagged: a payout happens only when these conditions are met, and on each eligible payout day the trader withdraws the maximum the rules allow (profit above the buffer, under the caps, never below the loss floor); balances and loss floors carry across payouts (see flag 'funded-withdrawal-model'). Omit for ungated payouts.",
"additionalProperties": {}
},
"profitSplitPct": {
"type": "number",
"maximum": 100,
"minimum": 0,
"description": "Trader's share of funded profits in PERCENT UNITS (80 = 80%)."
},
"payoutFrequency": {
"enum": [
"weekly",
"biweekly",
"monthly",
"on-demand"
],
"type": "string",
"description": "How often funded profits can be withdrawn."
},
"firstPayoutMinDays": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0,
"description": "Minimum days on the funded account before the first payout. Default 0."
}
},
"description": "Funded-stage terms used for the payout/EV simulation.",
"additionalProperties": {}
},
"maxLoss": {
"type": "object",
"required": [
"mode"
],
"properties": {
"pct": {
"type": "number",
"maximum": 100,
"description": "Max loss in PERCENT UNITS of the initial account size (10 = 10%). Exactly one of pct/amount.",
"exclusiveMinimum": 0
},
"mode": {
"enum": [
"static-initial",
"trailing-realized-eod",
"trailing-intraday-unrealized",
"trailing-locks-at-initial"
],
"type": "string",
"description": "How the max-loss floor behaves - the single most consequential rule difference between firms. 'static-initial': floor fixed at initial balance minus the limit; never moves (classic CFD two-step). 'trailing-realized-eod': floor ratchets up with end-of-day balance highs; intraday highs do not move it. 'trailing-intraday-unrealized': floor trails the peak unrealized equity intraday and never stops trailing (futures-style; the most-miscalculated rule in the industry: it cuts pass probability dramatically). 'trailing-locks-at-initial': trails intraday peak equity until the floor reaches the initial balance, then freezes (common futures variant). Locking is also composable: locksAtInitial adds the same lock to an EOD trail, and lockOffsetAmount shifts the lock level to initial balance + that amount (e.g. 100 models 'stops trailing $100 above the start')."
},
"amount": {
"type": "number",
"description": "Max loss as a fixed currency amount (alternative to pct).",
"exclusiveMinimum": 0
},
"locksAtInitial": {
"type": "boolean",
"description": "For trailing modes: once the trailing floor climbs up to the initial balance (plus lockOffsetAmount), it locks there and stops trailing. Default false. 'trailing-locks-at-initial' locks by definition; set this to add the same lock to 'trailing-realized-eod' (e.g. an EOD trail that stops at the starting balance)."
},
"lockOffsetAmount": {
"type": "number",
"minimum": 0,
"description": "Currency offset of the lock level: the floor locks at initial balance + this amount, modeling rules like 'the trailing threshold stops $100 above the start'. Default 0. Only meaningful when the rule locks (mode 'trailing-locks-at-initial' or locksAtInitial=true)."
}
},
"description": "Challenge-level max loss rule applied to every step unless a step overrides it. Required.",
"additionalProperties": {}
},
"sources": {
"type": "array",
"items": {
"type": "object",
"required": [
"url",
"lastVerified"
],
"properties": {
"url": {
"type": "string",
"description": "Public page documenting the rule."
},
"note": {
"type": "string"
},
"lastVerified": {
"type": "string",
"description": "ISO date the rules were last checked against that page."
}
},
"additionalProperties": {}
},
"description": "Public citations. Optional for inline specs; dataset entries always carry them."
},
"currency": {
"type": "string",
"description": "ISO currency code all amounts are denominated in. Default USD."
},
"dailyLoss": {
"anyOf": [
{
"type": "object",
"properties": {
"pct": {
"type": "number",
"maximum": 100,
"description": "Daily loss limit in PERCENT UNITS (5 = 5%); what it is a percent OF is set by limitBasis. Exactly one of pct/amount.",
"exclusiveMinimum": 0
},
"basis": {
"enum": [
"prior-day-balance",
"prior-day-equity"
],
"type": "string",
"description": "Anchor today's loss is measured from: prior day's closing balance or closing equity (they differ only with overnight positions). Default 'prior-day-balance'."
},
"amount": {
"type": "number",
"description": "Daily loss limit as a fixed currency amount (alternative to pct).",
"exclusiveMinimum": 0
},
"evaluation": {
"enum": [
"intraday",
"end-of-day"
],
"type": "string",
"description": "'intraday': fails the moment equity touches the daily floor. 'end-of-day': only the close is checked. Default 'intraday'."
},
"limitBasis": {
"enum": [
"initial-balance",
"anchor"
],
"type": "string",
"description": "What a percentage limit is a percent OF. 'initial-balance': a fixed currency allowance (always e.g. 5% of the starting account). 'anchor': recomputed daily from the day's anchor. Default 'initial-balance'."
},
"includesOpenPnl": {
"type": "boolean",
"description": "Whether floating (unrealized) P&L counts toward the daily loss, i.e. breach can happen intra-position. Default true."
}
},
"description": "Daily loss rule: the daily floor is anchor minus limit, reset at each trading-day boundary. Exactly one of pct/amount must be set.",
"additionalProperties": {}
},
{
"type": "null"
}
],
"description": "Challenge-level daily loss rule applied to every step unless a step overrides it. null = no daily loss rule. This field is required (pass null explicitly for none)."
},
"accountSize": {
"type": "number",
"description": "Initial account balance in account currency.",
"exclusiveMinimum": 0
},
"challengeId": {
"type": "string",
"minLength": 1,
"description": "Stable kebab-case id for this ruleset, e.g. '100k-2step'."
},
"constraints": {
"type": "object",
"description": "Informational trading constraints (maxLeverage, newsTrading, weekendHolding, ...). Recorded and flagged, never simulated.",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
},
"productType": {
"enum": [
"futures",
"cfd",
"equities"
],
"type": "string",
"description": "Instrument class the challenge is traded on: 'futures', 'cfd' (forex/CFD), or 'equities'."
},
"flagsNotSimulated": {
"type": "array",
"items": {
"type": "string"
},
"description": "Honesty channel: ids of rules this entry has that the engine does not simulate (e.g. 'scaling-plan', 'soft-daily-lockout'). Surfaced in every result's assumption flags. Consistency rules and payout gating do NOT belong here - the engine simulates them."
}
},
"description": "Inline challenge ruleset, for challenges not in the directory or for what-if rule edits. Mutually exclusive with firmId/challengeId. Identify the challenge EITHER by directory reference (firmId + challengeId, discovered via propfirms_list_simulatable; firmId accepts the directory id or the firm's name) OR by a full inline `spec` object - the exact shape propfirms_challenge_rules returns, so you can fetch a directory entry, change one rule, and re-simulate to model rule variations. Provide exactly one of the two forms; providing both or neither is an error. Directory references need network access; inline specs are fully offline.",
"additionalProperties": {}
},
"paths": {
"type": "integer",
"maximum": 100000,
"minimum": 100,
"description": "Monte Carlo paths (independent simulated trader journeys). Default 10,000 (well under a second); capped at 100,000 per tool call. Confidence intervals shrink roughly with the square root of paths."
},
"firmId": {
"type": "string",
"minLength": 1,
"description": "Directory firm id or firm name (e.g. 'ftmo' or 'FTMO'); discover with propfirms_list_simulatable. Must be paired with challengeId. Mutually exclusive with `spec`."
},
"avgWinR": {
"type": "number",
"description": "Average winning trade in R-multiples, i.e. multiples of the amount risked per trade (1.5 = winners average 1.5x the risk).",
"exclusiveMinimum": 0
},
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
},
"winRate": {
"type": "number",
"maximum": 1,
"minimum": 0,
"description": "Probability a trade is a winner, as a FRACTION in [0, 1] (0.55 = 55% winners) - NOT percent units. The most impactful input: traders routinely overestimate it by a few points, which can flip EV negative, so prefer measured stats over self-reported ones."
},
"winStdR": {
"type": "number",
"minimum": 0,
"description": "Standard deviation of winner sizes in R (0 = every winner is exactly avgWinR). Default 0. Adding spread makes streak damage more realistic."
},
"avgLossR": {
"type": "number",
"description": "Average losing trade in R, as a POSITIVE number. Default 1 (losers lose exactly the risked amount, i.e. stops are honored). Raise above 1 to model slippage or blown stops.",
"exclusiveMinimum": 0
},
"lossStdR": {
"type": "number",
"minimum": 0,
"description": "Standard deviation of loser sizes in R (0 = every loser is exactly avgLossR). Default 0."
},
"riskMode": {
"enum": [
"percent-of-balance",
"percent-of-initial",
"fixed-amount"
],
"type": "string",
"description": "How riskValue is interpreted. 'percent-of-balance' (default): risk compounds with the current balance. 'percent-of-initial': constant currency risk derived from the initial account size - how most prop traders size, since loss limits are fixed in currency. 'fixed-amount': explicit currency risked per 1R."
},
"riskValue": {
"type": "number",
"description": "Risk per trade - the value of 1R. PERCENT UNITS for percent modes (0.5 = 0.5% risked per trade; a typical prop range is 0.25-2), or a currency amount for 'fixed-amount'. NOT a fraction.",
"exclusiveMinimum": 0
},
"attemptCap": {
"type": "integer",
"maximum": 1000,
"minimum": 1,
"description": "Maximum challenge attempts per path before that path gives up. Default 25. Journey statistics (expected attempts/cost, P(funded)) are censored at this cap."
},
"challengeId": {
"type": "string",
"minLength": 1,
"description": "Directory challenge id; discover with propfirms_list_simulatable. Must be paired with firmId. Mutually exclusive with `spec`."
},
"tradesPerDay": {
"type": "number",
"description": "Average trades per simulated trading day. More trades per day means more ways to hit the daily loss limit within a single day.",
"exclusiveMinimum": 0
},
"simulateFunded": {
"type": "boolean",
"description": "Whether to simulate the funded stage (payouts, blowup risk) after passing. Default true - EV is only meaningful with it on; set false to study the evaluation alone."
},
"fundedHorizonDays": {
"type": "integer",
"maximum": 2000,
"minimum": 1,
"description": "Funded-stage horizon in trading days for the payout/EV simulation. Default 90 (about 4 calendar months). EV scales with this choice - state it when reporting EV."
},
"includeHistograms": {
"type": "boolean",
"description": "Include histogram arrays (attempts, cost, net, drawdown) in the result. Default FALSE for this tool to keep responses compact; summary quantiles (p05...p95) are always included."
},
"tradesPerDayModel": {
"enum": [
"fixed",
"poisson"
],
"type": "string",
"description": "'fixed' (default): the same count every day. 'poisson': daily count drawn Poisson(tradesPerDay); days can then have zero trades, which do not count as trading days."
}
}
}| Argument | Type | Description |
|---|---|---|
| seed | any | RNG seed (integer or string). Default 42. Same inputs + seed reproduce byte-identical results - include the seed when reporting so users can reproduce the numbers. |
| spec | object | Inline challenge ruleset, for challenges not in the directory or for what-if rule edits. Mutually exclusive with firmId/challengeId. Identify the challenge EITHER by directory reference (firmId + challengeId, discovered via propfirms_list_simulatable; firmId accepts the directory id or the firm's name) OR by a full inline `spec` object - the exact shape propfirms_challenge_rules returns, so you can fetch a directory entry, change one rule, and re-simulate to model rule variations. Provide exactly one of the two forms; providing both or neither is an error. Directory references need network access; inline specs are fully offline. |
| paths | integer | Monte Carlo paths (independent simulated trader journeys). Default 10,000 (well under a second); capped at 100,000 per tool call. Confidence intervals shrink roughly with the square root of paths. |
| firmId | string | Directory firm id or firm name (e.g. 'ftmo' or 'FTMO'); discover with propfirms_list_simulatable. Must be paired with challengeId. Mutually exclusive with `spec`. |
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
| rSeries | array | The trader's real trades as R-multiples in chronological order: each trade's P&L divided by the amount risked on it (+1.8 = won 1.8x risk, -1 = lost exactly the risk, -1.4 = stop slipped 40%). At least 10 trades; 100+ strongly recommended - short series make the simulation overconfident in the sample. Mutually exclusive with rSeriesText, tradeLogText, and tradeLogTexts. |
| riskMode | string | How riskValue is interpreted. 'percent-of-balance' (default): risk compounds with the current balance. 'percent-of-initial': constant currency risk derived from the initial account size - how most prop traders size, since loss limits are fixed in currency. 'fixed-amount': explicit currency risked per 1R. |
| riskValue* | number | Risk per trade - the value of 1R. PERCENT UNITS for percent modes (0.5 = 0.5% risked per trade; a typical prop range is 0.25-2), or a currency amount for 'fixed-amount'. NOT a fraction. |
| attemptCap | integer | Maximum challenge attempts per path before that path gives up. Default 25. Journey statistics (expected attempts/cost, P(funded)) are censored at this cap. |
| importRisk | string | Risk per trade for imports that carry P&L but no risk data (e.g. TradingView, MT5 deals, broker JSON, ThinkOrSwim): cash risked per trade ("25") or a percent of entry value ("1%"). Applies to tradeLogText/tradeLogTexts only, is labeled rSource inferred, and is never applied silently: without it such files are refused with needs-risk. |
| newsFilter | object | What-if comparison: what are my odds if I do not OPEN trades around scheduled news? Requires a timestamped input (tradeLogText or tradeLogTexts). The simulation runs TWICE with the same seed and options, once on the full history and once with every trade opened inside [event - preMinutes, event + postMinutes] removed; trades opened earlier but held through an event are only counted, not removed. The returned SimResult is the news-AVOIDED scenario; structuredContent.newsComparison carries both scenarios' headline numbers, the excluded-trade count, and a calendar caveat that MUST be relayed to the user (the calendar is a recurring-template approximation of scheduled releases, not a historical feed). |
| challengeId | string | Directory challenge id; discover with propfirms_list_simulatable. Must be paired with firmId. Mutually exclusive with `spec`. |
| rSeriesText | string | The same series as pasted text: a JSON array, CSV, or whitespace/newline separated numbers, with an optional 'R' suffix per value (e.g. "1.8R, -1R, 0.4, 2.1"). Parsed with the library's parseRSeries; unparseable tokens are reported back. Mutually exclusive with rSeries, tradeLogText, and tradeLogTexts. |
| tradeLogText | string | The trader's trades as one pasted TIMESTAMPED log instead of a bare series. Accepted formats, auto-detected: the generic CSV template (header: open time,close time,symbol,direction,quantity,entry price,exit price,stop loss,pnl,fees,r), plain timestamped CSV/TSV logs (open time + R columns), real platform exports: TradingView strategy-tester list of trades (both generations), MT4/MT5 account statements (CSV or pasted HTML), MT5 deals tables, and ThinkOrSwim account statements, plus broker trade-history JSON in the @luxalgo/broker-sdk shape (a bare fills array, {"trades": [...]}, or one snapshot account; fills replay FIFO into round trips with price-based P&L, disclosed). Timestamps WITHOUT an explicit offset are read as UTC. Files that carry P&L but no risk information need importRisk to become R-multiples; ambiguous rule readings are refused with diagnostics rather than guessed, and skipped rows are reported as warnings. Timestamps unlock two things a bare series cannot do: tradesPerDay is derived from the log when not given, and newsFilter can compare odds with and without trading around news. Mutually exclusive with rSeries, rSeriesText, and tradeLogTexts. |
| tradesPerDay | number | Average trades per simulated trading day. REQUIRED with rSeries/rSeriesText, which carry no timestamps. Optional with tradeLogText/tradeLogTexts: when omitted it is derived from the log's own timestamps (trades divided by distinct UTC trading days) and the output says so. More trades per day means more ways to hit the daily loss limit within a single day. |
| tradeLogTexts | array | PORTFOLIO MODE: 2 to 5 timestamped trade logs (same format as tradeLogText), one per strategy or account. They are merged into one chronological series and the combined account is simulated, which preserves cross-strategy loss clustering (exactly what daily and max loss limits punish). Overlap across the histories is ALWAYS analyzed and attached as structuredContent.portfolioOverlap with an audit-risk verdict; see the attached structuredContent.portfolioOverlap analysis for the methodology. Mutually exclusive with rSeries, rSeriesText, and tradeLogText. |
| simulateFunded | boolean | Whether to simulate the funded stage (payouts, blowup risk) after passing. Default true - EV is only meaningful with it on; set false to study the evaluation alone. |
| blockMeanLength | number | Mean block length of the stationary bootstrap (geometrically distributed blocks). Default 5 trades. 1 = i.i.d. resampling (destroys streaks - only for comparison); raise toward 10 if the trader's edge comes and goes in long regimes. |
| fundedHorizonDays | integer | Funded-stage horizon in trading days for the payout/EV simulation. Default 90 (about 4 calendar months). EV scales with this choice - state it when reporting EV. |
| includeHistograms | boolean | Include histogram arrays (attempts, cost, net, drawdown) in the result. Default FALSE for this tool to keep responses compact; summary quantiles (p05...p95) are always included. |
| tradesPerDayModel | string | 'fixed' (default): the same count every day. 'poisson': daily count drawn Poisson(tradesPerDay); days can then have zero trades, which do not count as trading days. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"riskValue",
"context"
],
"properties": {
"seed": {
"anyOf": [
{
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991
},
{
"type": "string"
}
],
"description": "RNG seed (integer or string). Default 42. Same inputs + seed reproduce byte-identical results - include the seed when reporting so users can reproduce the numbers."
},
"spec": {
"type": "object",
"required": [
"challengeId",
"name",
"accountSize",
"steps",
"dailyLoss",
"maxLoss",
"fees",
"funded"
],
"properties": {
"fees": {
"type": "object",
"required": [
"price"
],
"properties": {
"price": {
"type": "number",
"minimum": 0,
"description": "Challenge price in account currency. Under 'monthly' billing: price per month."
},
"billing": {
"enum": [
"one-time",
"monthly"
],
"type": "string",
"description": "'one-time' (default): the price buys one attempt; failed attempts are re-bought or reset. 'monthly': recurring subscription while evaluating (common for futures firms)."
},
"resetFee": {
"anyOf": [
{
"type": "number",
"minimum": 0
},
{
"type": "null"
}
],
"description": "Discounted fee to reset a failed attempt. null (default) = no reset offer: a failed one-time attempt costs full price again; a failed monthly attempt rides on the subscription."
},
"activationFee": {
"type": "number",
"minimum": 0,
"description": "One-time fee charged when the funded account is activated. Default 0."
},
"refundableOnPass": {
"type": "boolean",
"description": "Whether the one-time challenge fee is refunded once funded (credited back in cost/EV). Default false."
}
},
"description": "Fees - everything that goes into expected total cost.",
"additionalProperties": {}
},
"name": {
"type": "string",
"minLength": 1,
"description": "Display name, e.g. '100K 2-Step'."
},
"steps": {
"type": "array",
"items": {
"type": "object",
"properties": {
"maxDays": {
"anyOf": [
{
"type": "integer",
"maximum": 9007199254740991,
"exclusiveMinimum": 0
},
{
"type": "null"
}
],
"description": "Trading-day limit for the step; null (the default) = unlimited time."
},
"maxLoss": {
"type": "object",
"required": [
"mode"
],
"properties": {
"pct": {
"type": "number",
"maximum": 100,
"description": "Max loss in PERCENT UNITS of the initial account size (10 = 10%). Exactly one of pct/amount.",
"exclusiveMinimum": 0
},
"mode": {
"enum": [
"static-initial",
"trailing-realized-eod",
"trailing-intraday-unrealized",
"trailing-locks-at-initial"
],
"type": "string",
"description": "How the max-loss floor behaves - the single most consequential rule difference between firms. 'static-initial': floor fixed at initial balance minus the limit; never moves (classic CFD two-step). 'trailing-realized-eod': floor ratchets up with end-of-day balance highs; intraday highs do not move it. 'trailing-intraday-unrealized': floor trails the peak unrealized equity intraday and never stops trailing (futures-style; the most-miscalculated rule in the industry: it cuts pass probability dramatically). 'trailing-locks-at-initial': trails intraday peak equity until the floor reaches the initial balance, then freezes (common futures variant). Locking is also composable: locksAtInitial adds the same lock to an EOD trail, and lockOffsetAmount shifts the lock level to initial balance + that amount (e.g. 100 models 'stops trailing $100 above the start')."
},
"amount": {
"type": "number",
"description": "Max loss as a fixed currency amount (alternative to pct).",
"exclusiveMinimum": 0
},
"locksAtInitial": {
"type": "boolean",
"description": "For trailing modes: once the trailing floor climbs up to the initial balance (plus lockOffsetAmount), it locks there and stops trailing. Default false. 'trailing-locks-at-initial' locks by definition; set this to add the same lock to 'trailing-realized-eod' (e.g. an EOD trail that stops at the starting balance)."
},
"lockOffsetAmount": {
"type": "number",
"minimum": 0,
"description": "Currency offset of the lock level: the floor locks at initial balance + this amount, modeling rules like 'the trailing threshold stops $100 above the start'. Default 0. Only meaningful when the rule locks (mode 'trailing-locks-at-initial' or locksAtInitial=true)."
}
},
"description": "Per-step override of the challenge-level max loss rule. Omit to inherit.",
"additionalProperties": {}
},
"dailyLoss": {
"anyOf": [
{
"type": "object",
"properties": {
"pct": {
"type": "number",
"maximum": 100,
"description": "Daily loss limit in PERCENT UNITS (5 = 5%); what it is a percent OF is set by limitBasis. Exactly one of pct/amount.",
"exclusiveMinimum": 0
},
"basis": {
"enum": [
"prior-day-balance",
"prior-day-equity"
],
"type": "string",
"description": "Anchor today's loss is measured from: prior day's closing balance or closing equity (they differ only with overnight positions). Default 'prior-day-balance'."
},
"amount": {
"type": "number",
"description": "Daily loss limit as a fixed currency amount (alternative to pct).",
"exclusiveMinimum": 0
},
"evaluation": {
"enum": [
"intraday",
"end-of-day"
],
"type": "string",
"description": "'intraday': fails the moment equity touches the daily floor. 'end-of-day': only the close is checked. Default 'intraday'."
},
"limitBasis": {
"enum": [
"initial-balance",
"anchor"
],
"type": "string",
"description": "What a percentage limit is a percent OF. 'initial-balance': a fixed currency allowance (always e.g. 5% of the starting account). 'anchor': recomputed daily from the day's anchor. Default 'initial-balance'."
},
"includesOpenPnl": {
"type": "boolean",
"description": "Whether floating (unrealized) P&L counts toward the daily loss, i.e. breach can happen intra-position. Default true."
}
},
"description": "Daily loss rule: the daily floor is anchor minus limit, reset at each trading-day boundary. Exactly one of pct/amount must be set.",
"additionalProperties": {}
},
{
"type": "null"
}
],
"description": "Per-step override of the challenge-level daily loss rule. Omit to inherit; null = no daily loss rule in this step."
},
"consistency": {
"anyOf": [
{
"type": "object",
"required": [
"maxBestDayProfitPct"
],
"properties": {
"maxBestDayProfitPct": {
"type": "number",
"maximum": 100,
"description": "Maximum share of the step's total profit the best single day may contribute, in PERCENT UNITS (40 = the best day may be at most 40% of total profit).",
"exclusiveMinimum": 0
}
},
"additionalProperties": {}
},
{
"type": "null"
}
],
"description": "Consistency rule - SIMULATED (engine v1), not just flagged: one outsized day effectively raises the target (total profit must reach best day / pct), and the simulated trader keeps trading - rationally stopping days early when that helps - until the best-day share complies (see flag 'consistency-stop-rule'). null or omitted = no consistency rule."
},
"minTradingDays": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0,
"description": "Minimum days with at least one trade before the step can be passed. Default 0."
},
"profitTargetPct": {
"type": "number",
"description": "Profit target in PERCENT UNITS of the initial account size (8 = 8%). Exactly one of profitTargetPct/profitTargetAmount.",
"exclusiveMinimum": 0
},
"profitTargetAmount": {
"type": "number",
"description": "Profit target as a fixed currency amount (alternative to profitTargetPct).",
"exclusiveMinimum": 0
}
},
"description": "One evaluation step. Each step starts on a fresh account at the initial balance.",
"additionalProperties": {}
},
"minItems": 1,
"description": "Evaluation steps in order. Passing the last step means funded."
},
"funded": {
"type": "object",
"required": [
"profitSplitPct",
"payoutFrequency"
],
"properties": {
"notes": {
"type": "string",
"description": "Free-text funded-stage details that are not simulated."
},
"maxLoss": {
"type": "object",
"required": [
"mode"
],
"properties": {
"pct": {
"type": "number",
"maximum": 100,
"description": "Max loss in PERCENT UNITS of the initial account size (10 = 10%). Exactly one of pct/amount.",
"exclusiveMinimum": 0
},
"mode": {
"enum": [
"static-initial",
"trailing-realized-eod",
"trailing-intraday-unrealized",
"trailing-locks-at-initial"
],
"type": "string",
"description": "How the max-loss floor behaves - the single most consequential rule difference between firms. 'static-initial': floor fixed at initial balance minus the limit; never moves (classic CFD two-step). 'trailing-realized-eod': floor ratchets up with end-of-day balance highs; intraday highs do not move it. 'trailing-intraday-unrealized': floor trails the peak unrealized equity intraday and never stops trailing (futures-style; the most-miscalculated rule in the industry: it cuts pass probability dramatically). 'trailing-locks-at-initial': trails intraday peak equity until the floor reaches the initial balance, then freezes (common futures variant). Locking is also composable: locksAtInitial adds the same lock to an EOD trail, and lockOffsetAmount shifts the lock level to initial balance + that amount (e.g. 100 models 'stops trailing $100 above the start')."
},
"amount": {
"type": "number",
"description": "Max loss as a fixed currency amount (alternative to pct).",
"exclusiveMinimum": 0
},
"locksAtInitial": {
"type": "boolean",
"description": "For trailing modes: once the trailing floor climbs up to the initial balance (plus lockOffsetAmount), it locks there and stops trailing. Default false. 'trailing-locks-at-initial' locks by definition; set this to add the same lock to 'trailing-realized-eod' (e.g. an EOD trail that stops at the starting balance)."
},
"lockOffsetAmount": {
"type": "number",
"minimum": 0,
"description": "Currency offset of the lock level: the floor locks at initial balance + this amount, modeling rules like 'the trailing threshold stops $100 above the start'. Default 0. Only meaningful when the rule locks (mode 'trailing-locks-at-initial' or locksAtInitial=true)."
}
},
"description": "Funded-account override of the max loss rule. Omit to inherit.",
"additionalProperties": {}
},
"dailyLoss": {
"anyOf": [
{
"type": "object",
"properties": {
"pct": {
"type": "number",
"maximum": 100,
"description": "Daily loss limit in PERCENT UNITS (5 = 5%); what it is a percent OF is set by limitBasis. Exactly one of pct/amount.",
"exclusiveMinimum": 0
},
"basis": {
"enum": [
"prior-day-balance",
"prior-day-equity"
],
"type": "string",
"description": "Anchor today's loss is measured from: prior day's closing balance or closing equity (they differ only with overnight positions). Default 'prior-day-balance'."
},
"amount": {
"type": "number",
"description": "Daily loss limit as a fixed currency amount (alternative to pct).",
"exclusiveMinimum": 0
},
"evaluation": {
"enum": [
"intraday",
"end-of-day"
],
"type": "string",
"description": "'intraday': fails the moment equity touches the daily floor. 'end-of-day': only the close is checked. Default 'intraday'."
},
"limitBasis": {
"enum": [
"initial-balance",
"anchor"
],
"type": "string",
"description": "What a percentage limit is a percent OF. 'initial-balance': a fixed currency allowance (always e.g. 5% of the starting account). 'anchor': recomputed daily from the day's anchor. Default 'initial-balance'."
},
"includesOpenPnl": {
"type": "boolean",
"description": "Whether floating (unrealized) P&L counts toward the daily loss, i.e. breach can happen intra-position. Default true."
}
},
"description": "Daily loss rule: the daily floor is anchor minus limit, reset at each trading-day boundary. Exactly one of pct/amount must be set.",
"additionalProperties": {}
},
{
"type": "null"
}
],
"description": "Funded-account override of the daily loss rule. Omit to inherit; null = none."
},
"payoutRules": {
"type": "object",
"properties": {
"bufferAmount": {
"type": "number",
"minimum": 0,
"description": "Profit buffer that must remain in the account; only profit above it is withdrawable. Default 0."
},
"minWinningDays": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0,
"description": "Winning days required in a payout window before a payout can be requested. Default 0."
},
"maxPayoutAmount": {
"type": "number",
"description": "Absolute currency cap per payout request. Omit for no fixed cap.",
"exclusiveMinimum": 0
},
"winningDayMinProfit": {
"type": "number",
"minimum": 0,
"description": "Minimum profit for a day to count as a winning day. Default 0 (any positive day)."
},
"maxPayoutPctOfProfit": {
"type": "number",
"maximum": 100,
"description": "Cap on each payout in PERCENT UNITS of accrued profit (50 = at most half the profit per request). Omit for no percentage cap.",
"exclusiveMinimum": 0
},
"consistencyMaxBestDayPct": {
"type": "number",
"maximum": 100,
"description": "Funded consistency gate in PERCENT UNITS: the best day may contribute at most this share of the payout window's profit. Evaluated per window (see flag 'funded-consistency-window-approximated').",
"exclusiveMinimum": 0
}
},
"description": "Payout gating - SIMULATED (engine v1), not just flagged: a payout happens only when these conditions are met, and on each eligible payout day the trader withdraws the maximum the rules allow (profit above the buffer, under the caps, never below the loss floor); balances and loss floors carry across payouts (see flag 'funded-withdrawal-model'). Omit for ungated payouts.",
"additionalProperties": {}
},
"profitSplitPct": {
"type": "number",
"maximum": 100,
"minimum": 0,
"description": "Trader's share of funded profits in PERCENT UNITS (80 = 80%)."
},
"payoutFrequency": {
"enum": [
"weekly",
"biweekly",
"monthly",
"on-demand"
],
"type": "string",
"description": "How often funded profits can be withdrawn."
},
"firstPayoutMinDays": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0,
"description": "Minimum days on the funded account before the first payout. Default 0."
}
},
"description": "Funded-stage terms used for the payout/EV simulation.",
"additionalProperties": {}
},
"maxLoss": {
"type": "object",
"required": [
"mode"
],
"properties": {
"pct": {
"type": "number",
"maximum": 100,
"description": "Max loss in PERCENT UNITS of the initial account size (10 = 10%). Exactly one of pct/amount.",
"exclusiveMinimum": 0
},
"mode": {
"enum": [
"static-initial",
"trailing-realized-eod",
"trailing-intraday-unrealized",
"trailing-locks-at-initial"
],
"type": "string",
"description": "How the max-loss floor behaves - the single most consequential rule difference between firms. 'static-initial': floor fixed at initial balance minus the limit; never moves (classic CFD two-step). 'trailing-realized-eod': floor ratchets up with end-of-day balance highs; intraday highs do not move it. 'trailing-intraday-unrealized': floor trails the peak unrealized equity intraday and never stops trailing (futures-style; the most-miscalculated rule in the industry: it cuts pass probability dramatically). 'trailing-locks-at-initial': trails intraday peak equity until the floor reaches the initial balance, then freezes (common futures variant). Locking is also composable: locksAtInitial adds the same lock to an EOD trail, and lockOffsetAmount shifts the lock level to initial balance + that amount (e.g. 100 models 'stops trailing $100 above the start')."
},
"amount": {
"type": "number",
"description": "Max loss as a fixed currency amount (alternative to pct).",
"exclusiveMinimum": 0
},
"locksAtInitial": {
"type": "boolean",
"description": "For trailing modes: once the trailing floor climbs up to the initial balance (plus lockOffsetAmount), it locks there and stops trailing. Default false. 'trailing-locks-at-initial' locks by definition; set this to add the same lock to 'trailing-realized-eod' (e.g. an EOD trail that stops at the starting balance)."
},
"lockOffsetAmount": {
"type": "number",
"minimum": 0,
"description": "Currency offset of the lock level: the floor locks at initial balance + this amount, modeling rules like 'the trailing threshold stops $100 above the start'. Default 0. Only meaningful when the rule locks (mode 'trailing-locks-at-initial' or locksAtInitial=true)."
}
},
"description": "Challenge-level max loss rule applied to every step unless a step overrides it. Required.",
"additionalProperties": {}
},
"sources": {
"type": "array",
"items": {
"type": "object",
"required": [
"url",
"lastVerified"
],
"properties": {
"url": {
"type": "string",
"description": "Public page documenting the rule."
},
"note": {
"type": "string"
},
"lastVerified": {
"type": "string",
"description": "ISO date the rules were last checked against that page."
}
},
"additionalProperties": {}
},
"description": "Public citations. Optional for inline specs; dataset entries always carry them."
},
"currency": {
"type": "string",
"description": "ISO currency code all amounts are denominated in. Default USD."
},
"dailyLoss": {
"anyOf": [
{
"type": "object",
"properties": {
"pct": {
"type": "number",
"maximum": 100,
"description": "Daily loss limit in PERCENT UNITS (5 = 5%); what it is a percent OF is set by limitBasis. Exactly one of pct/amount.",
"exclusiveMinimum": 0
},
"basis": {
"enum": [
"prior-day-balance",
"prior-day-equity"
],
"type": "string",
"description": "Anchor today's loss is measured from: prior day's closing balance or closing equity (they differ only with overnight positions). Default 'prior-day-balance'."
},
"amount": {
"type": "number",
"description": "Daily loss limit as a fixed currency amount (alternative to pct).",
"exclusiveMinimum": 0
},
"evaluation": {
"enum": [
"intraday",
"end-of-day"
],
"type": "string",
"description": "'intraday': fails the moment equity touches the daily floor. 'end-of-day': only the close is checked. Default 'intraday'."
},
"limitBasis": {
"enum": [
"initial-balance",
"anchor"
],
"type": "string",
"description": "What a percentage limit is a percent OF. 'initial-balance': a fixed currency allowance (always e.g. 5% of the starting account). 'anchor': recomputed daily from the day's anchor. Default 'initial-balance'."
},
"includesOpenPnl": {
"type": "boolean",
"description": "Whether floating (unrealized) P&L counts toward the daily loss, i.e. breach can happen intra-position. Default true."
}
},
"description": "Daily loss rule: the daily floor is anchor minus limit, reset at each trading-day boundary. Exactly one of pct/amount must be set.",
"additionalProperties": {}
},
{
"type": "null"
}
],
"description": "Challenge-level daily loss rule applied to every step unless a step overrides it. null = no daily loss rule. This field is required (pass null explicitly for none)."
},
"accountSize": {
"type": "number",
"description": "Initial account balance in account currency.",
"exclusiveMinimum": 0
},
"challengeId": {
"type": "string",
"minLength": 1,
"description": "Stable kebab-case id for this ruleset, e.g. '100k-2step'."
},
"constraints": {
"type": "object",
"description": "Informational trading constraints (maxLeverage, newsTrading, weekendHolding, ...). Recorded and flagged, never simulated.",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
},
"productType": {
"enum": [
"futures",
"cfd",
"equities"
],
"type": "string",
"description": "Instrument class the challenge is traded on: 'futures', 'cfd' (forex/CFD), or 'equities'."
},
"flagsNotSimulated": {
"type": "array",
"items": {
"type": "string"
},
"description": "Honesty channel: ids of rules this entry has that the engine does not simulate (e.g. 'scaling-plan', 'soft-daily-lockout'). Surfaced in every result's assumption flags. Consistency rules and payout gating do NOT belong here - the engine simulates them."
}
},
"description": "Inline challenge ruleset, for challenges not in the directory or for what-if rule edits. Mutually exclusive with firmId/challengeId. Identify the challenge EITHER by directory reference (firmId + challengeId, discovered via propfirms_list_simulatable; firmId accepts the directory id or the firm's name) OR by a full inline `spec` object - the exact shape propfirms_challenge_rules returns, so you can fetch a directory entry, change one rule, and re-simulate to model rule variations. Provide exactly one of the two forms; providing both or neither is an error. Directory references need network access; inline specs are fully offline.",
"additionalProperties": {}
},
"paths": {
"type": "integer",
"maximum": 100000,
"minimum": 100,
"description": "Monte Carlo paths (independent simulated trader journeys). Default 10,000 (well under a second); capped at 100,000 per tool call. Confidence intervals shrink roughly with the square root of paths."
},
"firmId": {
"type": "string",
"minLength": 1,
"description": "Directory firm id or firm name (e.g. 'ftmo' or 'FTMO'); discover with propfirms_list_simulatable. Must be paired with challengeId. Mutually exclusive with `spec`."
},
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
},
"rSeries": {
"type": "array",
"items": {
"type": "number"
},
"minItems": 10,
"description": "The trader's real trades as R-multiples in chronological order: each trade's P&L divided by the amount risked on it (+1.8 = won 1.8x risk, -1 = lost exactly the risk, -1.4 = stop slipped 40%). At least 10 trades; 100+ strongly recommended - short series make the simulation overconfident in the sample. Mutually exclusive with rSeriesText, tradeLogText, and tradeLogTexts."
},
"riskMode": {
"enum": [
"percent-of-balance",
"percent-of-initial",
"fixed-amount"
],
"type": "string",
"description": "How riskValue is interpreted. 'percent-of-balance' (default): risk compounds with the current balance. 'percent-of-initial': constant currency risk derived from the initial account size - how most prop traders size, since loss limits are fixed in currency. 'fixed-amount': explicit currency risked per 1R."
},
"riskValue": {
"type": "number",
"description": "Risk per trade - the value of 1R. PERCENT UNITS for percent modes (0.5 = 0.5% risked per trade; a typical prop range is 0.25-2), or a currency amount for 'fixed-amount'. NOT a fraction.",
"exclusiveMinimum": 0
},
"attemptCap": {
"type": "integer",
"maximum": 1000,
"minimum": 1,
"description": "Maximum challenge attempts per path before that path gives up. Default 25. Journey statistics (expected attempts/cost, P(funded)) are censored at this cap."
},
"importRisk": {
"type": "string",
"description": "Risk per trade for imports that carry P&L but no risk data (e.g. TradingView, MT5 deals, broker JSON, ThinkOrSwim): cash risked per trade (\"25\") or a percent of entry value (\"1%\"). Applies to tradeLogText/tradeLogTexts only, is labeled rSource inferred, and is never applied silently: without it such files are refused with needs-risk."
},
"newsFilter": {
"type": "object",
"properties": {
"impacts": {
"type": "array",
"items": {
"enum": [
"low",
"medium",
"high"
],
"type": "string"
},
"minItems": 1,
"description": "Impact levels to avoid. Default ['high']. The built-in recurring calendar carries high- and medium-impact templates only; 'low' matches nothing unless customEventTimes supplies the events."
},
"currencies": {
"type": "array",
"items": {
"enum": [
"USD",
"EUR",
"GBP",
"JPY",
"AUD",
"CAD",
"CHF",
"NZD"
],
"type": "string"
},
"minItems": 1,
"description": "Currencies whose events are avoided. Default: all eight built-in currencies (USD, EUR, GBP, JPY, AUD, CAD, CHF, NZD)."
},
"preMinutes": {
"type": "number",
"maximum": 1440,
"minimum": 0,
"description": "Minutes avoided BEFORE each event. Default 30."
},
"postMinutes": {
"type": "number",
"maximum": 1440,
"minimum": 0,
"description": "Minutes avoided AFTER each event. Default 30."
},
"customEventTimes": {
"type": "array",
"items": {
"type": "number"
},
"description": "Exact extra event times as epoch MILLISECONDS UTC, merged into the calendar as high-impact events. Use these for releases the recurring templates do not cover."
}
},
"description": "What-if comparison: what are my odds if I do not OPEN trades around scheduled news? Requires a timestamped input (tradeLogText or tradeLogTexts). The simulation runs TWICE with the same seed and options, once on the full history and once with every trade opened inside [event - preMinutes, event + postMinutes] removed; trades opened earlier but held through an event are only counted, not removed. The returned SimResult is the news-AVOIDED scenario; structuredContent.newsComparison carries both scenarios' headline numbers, the excluded-trade count, and a calendar caveat that MUST be relayed to the user (the calendar is a recurring-template approximation of scheduled releases, not a historical feed)."
},
"challengeId": {
"type": "string",
"minLength": 1,
"description": "Directory challenge id; discover with propfirms_list_simulatable. Must be paired with firmId. Mutually exclusive with `spec`."
},
"rSeriesText": {
"type": "string",
"minLength": 1,
"description": "The same series as pasted text: a JSON array, CSV, or whitespace/newline separated numbers, with an optional 'R' suffix per value (e.g. \"1.8R, -1R, 0.4, 2.1\"). Parsed with the library's parseRSeries; unparseable tokens are reported back. Mutually exclusive with rSeries, tradeLogText, and tradeLogTexts."
},
"tradeLogText": {
"type": "string",
"minLength": 1,
"description": "The trader's trades as one pasted TIMESTAMPED log instead of a bare series. Accepted formats, auto-detected: the generic CSV template (header: open time,close time,symbol,direction,quantity,entry price,exit price,stop loss,pnl,fees,r), plain timestamped CSV/TSV logs (open time + R columns), real platform exports: TradingView strategy-tester list of trades (both generations), MT4/MT5 account statements (CSV or pasted HTML), MT5 deals tables, and ThinkOrSwim account statements, plus broker trade-history JSON in the @luxalgo/broker-sdk shape (a bare fills array, {\"trades\": [...]}, or one snapshot account; fills replay FIFO into round trips with price-based P&L, disclosed). Timestamps WITHOUT an explicit offset are read as UTC. Files that carry P&L but no risk information need importRisk to become R-multiples; ambiguous rule readings are refused with diagnostics rather than guessed, and skipped rows are reported as warnings. Timestamps unlock two things a bare series cannot do: tradesPerDay is derived from the log when not given, and newsFilter can compare odds with and without trading around news. Mutually exclusive with rSeries, rSeriesText, and tradeLogTexts."
},
"tradesPerDay": {
"type": "number",
"description": "Average trades per simulated trading day. REQUIRED with rSeries/rSeriesText, which carry no timestamps. Optional with tradeLogText/tradeLogTexts: when omitted it is derived from the log's own timestamps (trades divided by distinct UTC trading days) and the output says so. More trades per day means more ways to hit the daily loss limit within a single day.",
"exclusiveMinimum": 0
},
"tradeLogTexts": {
"type": "array",
"items": {
"type": "string",
"minLength": 1
},
"maxItems": 5,
"minItems": 2,
"description": "PORTFOLIO MODE: 2 to 5 timestamped trade logs (same format as tradeLogText), one per strategy or account. They are merged into one chronological series and the combined account is simulated, which preserves cross-strategy loss clustering (exactly what daily and max loss limits punish). Overlap across the histories is ALWAYS analyzed and attached as structuredContent.portfolioOverlap with an audit-risk verdict; see the attached structuredContent.portfolioOverlap analysis for the methodology. Mutually exclusive with rSeries, rSeriesText, and tradeLogText."
},
"simulateFunded": {
"type": "boolean",
"description": "Whether to simulate the funded stage (payouts, blowup risk) after passing. Default true - EV is only meaningful with it on; set false to study the evaluation alone."
},
"blockMeanLength": {
"type": "number",
"description": "Mean block length of the stationary bootstrap (geometrically distributed blocks). Default 5 trades. 1 = i.i.d. resampling (destroys streaks - only for comparison); raise toward 10 if the trader's edge comes and goes in long regimes.",
"exclusiveMinimum": 0
},
"fundedHorizonDays": {
"type": "integer",
"maximum": 2000,
"minimum": 1,
"description": "Funded-stage horizon in trading days for the payout/EV simulation. Default 90 (about 4 calendar months). EV scales with this choice - state it when reporting EV."
},
"includeHistograms": {
"type": "boolean",
"description": "Include histogram arrays (attempts, cost, net, drawdown) in the result. Default FALSE for this tool to keep responses compact; summary quantiles (p05...p95) are always included."
},
"tradesPerDayModel": {
"enum": [
"fixed",
"poisson"
],
"type": "string",
"description": "'fixed' (default): the same count every day. 'poisson': daily count drawn Poisson(tradesPerDay); days can then have zero trades, which do not count as trading days."
}
}
}| paths | integer | Monte Carlo paths PER CHALLENGE. Default 5,000 here (one full simulation runs per challenge in scope, so this tool costs number-of-challenges times one simulation); raise it to tighten confidence intervals on a narrowed scope. |
| avgWinR | number | Average winning trade in R-multiples, i.e. multiples of the amount risked per trade (1.5 = winners average 1.5x the risk). |
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
| rSeries | array | The strategy's real trades as R-multiples in chronological order (P&L divided by amount risked; +1.8 = won 1.8x risk, -1 = lost the risk). At least 10 trades, 100+ recommended. When given, the screen uses the stationary block bootstrap (streaks preserved) instead of winRate/avgWinR. |
| winRate | number | Probability a trade is a winner, as a FRACTION in [0, 1] (0.55 = 55% winners) — NOT percent units. The most impactful input: traders routinely overestimate it by a few points, which can flip EV negative, so prefer measured stats over self-reported ones. |
| winStdR | number | Standard deviation of winner sizes in R (0 = every winner is exactly avgWinR). Default 0. Adding spread makes streak damage more realistic. |
| avgLossR | number | Average losing trade in R, as a POSITIVE number. Default 1 (losers lose exactly the risked amount, i.e. stops are honored). Raise above 1 to model slippage or blown stops. |
| lossStdR | number | Standard deviation of loser sizes in R (0 = every loser is exactly avgLossR). Default 0. |
| priceMax | number | Only challenges costing at most this. |
| riskMode | string | How riskValue is interpreted. 'percent-of-balance' (default): risk compounds with the current balance. 'percent-of-initial': constant currency risk derived from the initial account size — how most prop traders size, since loss limits are fixed in currency. 'fixed-amount': explicit currency risked per 1R. |
| riskValue* | number | Risk per trade — the value of 1R. PERCENT UNITS for percent modes (0.5 = 0.5% risked per trade; a typical prop range is 0.25-2), or a currency amount for 'fixed-amount'. NOT a fraction. |
| attemptCap | integer | Maximum challenge attempts per path before that path gives up. Default 25. Journey statistics (expected attempts/cost, P(funded)) are censored at this cap. |
| productType | string | Restrict the screen to one instrument class. |
| rSeriesText | string | The same series as pasted text (JSON, CSV, or whitespace separated, optional 'R' suffix). Mutually exclusive with rSeries. |
| tradesPerDay* | number | Average trades per simulated trading day. More trades per day means more ways to hit the daily loss limit within a single day. |
| accountSizeMax | number | Only challenges with at most this account size. |
| accountSizeMin | number | Only challenges with at least this account size. |
| simulateFunded | boolean | Whether to simulate the funded stage (payouts, blowup risk) after passing. Default true — EV is only meaningful with it on; set false to study the evaluation alone. |
| blockMeanLength | number | Bootstrap mean block length in trades. Default 5. Only used with rSeries/rSeriesText. |
| fundedHorizonDays | integer | Funded-stage horizon in trading days for the payout/EV simulation. Default 90 (about 4 calendar months). EV scales with this choice — state it when reporting EV. |
| minPassPerAttempt | number | The pass bar as a FRACTION in [0, 1]: a challenge counts as passing when the simulated per-attempt pass probability is at least this. Default 0.5. State the bar when relaying results. |
| requirePositiveEv | boolean | Additionally require expected value (payouts minus all fees over the funded horizon) above zero. Default false. |
| tradesPerDayModel | string | 'fixed' (default): the same count every day. 'poisson': daily count drawn Poisson(tradesPerDay); days can then have zero trades, which do not count as trading days. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"tradesPerDay",
"riskValue",
"context"
],
"properties": {
"firm": {
"type": "string",
"minLength": 1,
"description": "Restrict to one firm by propfirmId or name (e.g. 'ftmo')."
},
"seed": {
"anyOf": [
{
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991
},
{
"type": "string"
}
],
"description": "RNG seed (integer or string). Default 42. Same inputs + seed reproduce byte-identical results — include the seed when reporting so users can reproduce the numbers."
},
"paths": {
"type": "integer",
"maximum": 20000,
"minimum": 100,
"description": "Monte Carlo paths PER CHALLENGE. Default 5,000 here (one full simulation runs per challenge in scope, so this tool costs number-of-challenges times one simulation); raise it to tighten confidence intervals on a narrowed scope."
},
"avgWinR": {
"type": "number",
"description": "Average winning trade in R-multiples, i.e. multiples of the amount risked per trade (1.5 = winners average 1.5x the risk).",
"exclusiveMinimum": 0
},
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
},
"rSeries": {
"type": "array",
"items": {
"type": "number"
},
"minItems": 10,
"description": "The strategy's real trades as R-multiples in chronological order (P&L divided by amount risked; +1.8 = won 1.8x risk, -1 = lost the risk). At least 10 trades, 100+ recommended. When given, the screen uses the stationary block bootstrap (streaks preserved) instead of winRate/avgWinR."
},
"winRate": {
"type": "number",
"maximum": 1,
"minimum": 0,
"description": "Probability a trade is a winner, as a FRACTION in [0, 1] (0.55 = 55% winners) — NOT percent units. The most impactful input: traders routinely overestimate it by a few points, which can flip EV negative, so prefer measured stats over self-reported ones."
},
"winStdR": {
"type": "number",
"minimum": 0,
"description": "Standard deviation of winner sizes in R (0 = every winner is exactly avgWinR). Default 0. Adding spread makes streak damage more realistic."
},
"avgLossR": {
"type": "number",
"description": "Average losing trade in R, as a POSITIVE number. Default 1 (losers lose exactly the risked amount, i.e. stops are honored). Raise above 1 to model slippage or blown stops.",
"exclusiveMinimum": 0
},
"lossStdR": {
"type": "number",
"minimum": 0,
"description": "Standard deviation of loser sizes in R (0 = every loser is exactly avgLossR). Default 0."
},
"priceMax": {
"type": "number",
"description": "Only challenges costing at most this.",
"exclusiveMinimum": 0
},
"riskMode": {
"enum": [
"percent-of-balance",
"percent-of-initial",
"fixed-amount"
],
"type": "string",
"description": "How riskValue is interpreted. 'percent-of-balance' (default): risk compounds with the current balance. 'percent-of-initial': constant currency risk derived from the initial account size — how most prop traders size, since loss limits are fixed in currency. 'fixed-amount': explicit currency risked per 1R."
},
"riskValue": {
"type": "number",
"description": "Risk per trade — the value of 1R. PERCENT UNITS for percent modes (0.5 = 0.5% risked per trade; a typical prop range is 0.25-2), or a currency amount for 'fixed-amount'. NOT a fraction.",
"exclusiveMinimum": 0
},
"attemptCap": {
"type": "integer",
"maximum": 1000,
"minimum": 1,
"description": "Maximum challenge attempts per path before that path gives up. Default 25. Journey statistics (expected attempts/cost, P(funded)) are censored at this cap."
},
"productType": {
"enum": [
"futures",
"cfd"
],
"type": "string",
"description": "Restrict the screen to one instrument class."
},
"rSeriesText": {
"type": "string",
"minLength": 1,
"description": "The same series as pasted text (JSON, CSV, or whitespace separated, optional 'R' suffix). Mutually exclusive with rSeries."
},
"tradesPerDay": {
"type": "number",
"description": "Average trades per simulated trading day. More trades per day means more ways to hit the daily loss limit within a single day.",
"exclusiveMinimum": 0
},
"accountSizeMax": {
"type": "number",
"description": "Only challenges with at most this account size.",
"exclusiveMinimum": 0
},
"accountSizeMin": {
"type": "number",
"description": "Only challenges with at least this account size.",
"exclusiveMinimum": 0
},
"simulateFunded": {
"type": "boolean",
"description": "Whether to simulate the funded stage (payouts, blowup risk) after passing. Default true — EV is only meaningful with it on; set false to study the evaluation alone."
},
"blockMeanLength": {
"type": "number",
"description": "Bootstrap mean block length in trades. Default 5. Only used with rSeries/rSeriesText.",
"exclusiveMinimum": 0
},
"fundedHorizonDays": {
"type": "integer",
"maximum": 2000,
"minimum": 1,
"description": "Funded-stage horizon in trading days for the payout/EV simulation. Default 90 (about 4 calendar months). EV scales with this choice — state it when reporting EV."
},
"minPassPerAttempt": {
"type": "number",
"maximum": 1,
"minimum": 0,
"description": "The pass bar as a FRACTION in [0, 1]: a challenge counts as passing when the simulated per-attempt pass probability is at least this. Default 0.5. State the bar when relaying results."
},
"requirePositiveEv": {
"type": "boolean",
"description": "Additionally require expected value (payouts minus all fees over the funded horizon) above zero. Default false."
},
"tradesPerDayModel": {
"enum": [
"fixed",
"poisson"
],
"type": "string",
"description": "'fixed' (default): the same count every day. 'poisson': daily count drawn Poisson(tradesPerDay); days can then have zero trades, which do not count as trading days."
}
}
}| string |
| Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
| dataset* | string | Dataset id, from trackers_datasets |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"dataset",
"context"
],
"properties": {
"sort": {
"enum": [
"newest",
"oldest"
],
"type": "string",
"description": "Order by event date (default newest)"
},
"text": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "Case-insensitive substring over the dataset's name/title fields (member, insider, issuer, recipient, registrant and client, sponsor, assignee, bill title, …); see textPaths in trackers_datasets"
},
"limit": {
"type": "integer",
"maximum": 100,
"minimum": 1,
"description": "Rows to return (default 25, max 100)"
},
"where": {
"type": "object",
"description": "Exact field matches by dot path, e.g. {\"side\":\"buy\"}, {\"member.state\":\"CA\"}, {\"code\":\"P\"}, {\"formType\":\"4\"}; string comparisons are case-insensitive, arrays match when any element does",
"propertyNames": {
"type": "string"
},
"additionalProperties": {
"type": [
"string",
"number",
"boolean"
]
}
},
"offset": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0,
"description": "Rows to skip, for paging (default 0)"
},
"ticker": {
"type": "string",
"maxLength": 12,
"minLength": 1,
"description": "Trading symbol, case-insensitive (e.g. 'NVDA'); matches the dataset's ticker field(s). Only datasets flagged tickerSearchable carry tickers."
},
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
},
"dataset": {
"enum": [
"congress-trades",
"insider-transactions",
"thirteenf-holdings",
"gov-contracts",
"gov-grants",
"lobbying-filings",
"short-volume",
"committee-assignments",
"patents",
"clinical-trials",
"fda-approvals",
"cot-reports",
"wiki-pageviews",
"bills",
"fec-candidates",
"fec-contributions",
"congress-hearings",
"fed-communications"
],
"type": "string",
"description": "Dataset id, from trackers_datasets"
}
}
}| Exact field matches by dot path, e.g. {"side":"buy"}, {"member.state":"CA"}, {"code":"P"}, {"formType":"4"}; string comparisons are case-insensitive, arrays match when any element does |
| years | array | Event years to read (max 8); default is the newest year with data. Prefer one year at a time for deep-history datasets. |
| offset | integer | Rows to skip, for paging (default 0) |
| ticker | string | Trading symbol, case-insensitive (e.g. 'NVDA'); matches the dataset's ticker field(s). Only datasets flagged tickerSearchable carry tickers. |
| context* | string | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." |
| dataset* | string | Dataset id, from trackers_datasets |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"dataset",
"context"
],
"properties": {
"sort": {
"enum": [
"newest",
"oldest"
],
"type": "string",
"description": "Order by event date (default newest)"
},
"text": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "Case-insensitive substring over the dataset's name/title fields (member, insider, issuer, recipient, registrant and client, sponsor, assignee, bill title, …); see textPaths in trackers_datasets"
},
"limit": {
"type": "integer",
"maximum": 100,
"minimum": 1,
"description": "Rows to return (default 25, max 100)"
},
"since": {
"type": "string",
"pattern": "^\\d{4}(-\\d{2}(-\\d{2})?)?$",
"description": "Earliest event date (YYYY-MM-DD, YYYY-MM or YYYY), inclusive"
},
"until": {
"type": "string",
"pattern": "^\\d{4}(-\\d{2}(-\\d{2})?)?$",
"description": "Latest event date, inclusive"
},
"where": {
"type": "object",
"description": "Exact field matches by dot path, e.g. {\"side\":\"buy\"}, {\"member.state\":\"CA\"}, {\"code\":\"P\"}, {\"formType\":\"4\"}; string comparisons are case-insensitive, arrays match when any element does",
"propertyNames": {
"type": "string"
},
"additionalProperties": {
"type": [
"string",
"number",
"boolean"
]
}
},
"years": {
"type": "array",
"items": {
"type": "integer",
"maximum": 2100,
"minimum": 1900
},
"maxItems": 8,
"description": "Event years to read (max 8); default is the newest year with data. Prefer one year at a time for deep-history datasets."
},
"offset": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0,
"description": "Rows to skip, for paging (default 0)"
},
"ticker": {
"type": "string",
"maxLength": 12,
"minLength": 1,
"description": "Trading symbol, case-insensitive (e.g. 'NVDA'); matches the dataset's ticker field(s). Only datasets flagged tickerSearchable carry tickers."
},
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
},
"dataset": {
"enum": [
"congress-trades",
"insider-transactions",
"thirteenf-holdings",
"gov-contracts",
"gov-grants",
"lobbying-filings",
"short-volume",
"committee-assignments",
"patents",
"clinical-trials",
"fda-approvals",
"cot-reports",
"wiki-pageviews",
"bills",
"fec-candidates",
"fec-contributions",
"congress-hearings",
"fed-communications"
],
"type": "string",
"description": "Dataset id, from trackers_datasets"
}
}
}{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"ticker",
"context"
],
"properties": {
"year": {
"type": "integer",
"maximum": 2100,
"minimum": 1900,
"description": "Event year to read (default: the current year)"
},
"limit": {
"type": "integer",
"maximum": 25,
"minimum": 1,
"description": "Newest rows to include per dataset (default 5)"
},
"ticker": {
"type": "string",
"maxLength": 12,
"minLength": 1,
"description": "Trading symbol, e.g. 'NVDA'"
},
"context": {
"type": "string",
"description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
}
}
}