developer-tools Static interface comparison

LuxAlgo MCP

1.5.0 2.0.0

REVIEWPending human review

1 schema change requires review.No new authority detected.

View the upgrade review as Markdown

A shareable summary of this comparison for an issue, pull request or ticket. Select the text and copy it.

Tools48 → 47
Added0
Removed1
Schema changes1
Input schema changes1
Output schema changes0
Unclassified schema changes0
Description changes10
New write authority0
New destructive authority0
New unknown authority0
AnalysisREVIEW

INTERFACE DIFF

What changed, tool by tool

Classification from the recorded findings · definitions from the published snapshots

11 tools with recorded changes

  1. journal_update_noteModifiedDescriptionINFO

    What changed

    • journal_update_note: description changed.

    Why it could matter

    • Models choose and call tools partly from their descriptions.

    What to verify

    • Spot-check that agents still select this tool as intended.
    Declared effect
    write → write
    Description
    PreviousReplace 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. Requires signing in with a LuxAlgo account (OAuth).
    CurrentReplace 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).

    Input schema

    Input schema unchanged.

    4 unchanged entries
    • (schema root)
    • body
    • date
    • noteId

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  2. journal_write_noteModifiedDescriptionINFO

    What changed

    • journal_write_note: description changed.

    Why it could matter

    • Models choose and call tools partly from their descriptions.

    What to verify

    • Spot-check that agents still select this tool as intended.
    Declared effect
    write → write
    Description
    PreviousAdd 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. Requires signing in with a LuxAlgo account (OAuth).
    CurrentAdd 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).

    Input schema

    Input schema unchanged.

    3 unchanged entries
    • (schema root)
    • body
    • date

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  3. library_list_conceptsModifiedDescriptionINFO

    What changed

    • library_list_concepts: description changed.

    Why it could matter

    • Models choose and call tools partly from their descriptions.

    What to verify

    • Spot-check that agents still select this tool as intended.
    Declared effect
    read → read
    Description
    PreviousBrowse 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.
    CurrentBrowse 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 and the concept filter of library_list_indicators; for keyword lookup prefer library_search.

    Input schema

    Input schema unchanged.

    4 unchanged entries
    • (schema root)
    • family
    • page
    • page_size

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  4. library_list_indicatorsModifiedSchemaDescriptionREVIEWINFO

    What changed

    • library_list_indicators — Schema change: input property removed: tags.
    • library_list_indicators — Schema change: input property concept changed: description "Concept slug — o… → "Concept slug (from….
    • library_list_indicators — Schema change: input property family changed: +description="Family key from li….
    • library_list_indicators: description changed.

    Why it could matter

    • Calls or consumers built for the earlier schema may need to change.
    • Models choose and call tools partly from their descriptions.

    What to verify

    • Validate representative existing tool calls against the new argument schema.
    • Spot-check that agents still select this tool as intended.
    Declared effect
    read → read
    Description
    PreviousBrowse 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.
    CurrentBrowse the indicator catalog with filters and server-side sorting (newest first by default). The Library is organized by family and concept: filter by family (keys from library_list_families) or by concept slug (that concept's implementations; slugs from library_list_concepts or library_search), and optionally by 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.

    Input schema

    PropertyPrevious (1.5.0)Current (2.0.0)Change
    conceptstringoptionalstringoptional
    • Description changed
    familystring, enum (17)optionalstring, enum (17)optional
    • Description changed
    tagsarrayoptionalnot present
    • Removed
    tags › [items]stringnot present
    • Removed
    8 unchanged entries
    • (schema root)
    • direction
    • page
    • page_size
    • platform
    • sort
    • text
    • tier

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  5. library_list_tagsRemovedRemovedREVIEW

    What changed

    • Tool library_list_tags was removed.

    Why it could matter

    • Integrations, prompts or agent configurations that call this tool will not find it in this release.

    What to verify

    • Check whether existing integrations still reference this tool.
    Declared effect
    read → —

    Input schema

    PropertyPrevious (1.5.0)Current (2.0.0)Change
    (schema root)objectnot present
    • Removed

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  6. propfirms_challenge_rulesModifiedDescriptionINFO

    What changed

    • propfirms_challenge_rules: description changed.

    Why it could matter

    • Models choose and call tools partly from their descriptions.

    What to verify

    • Spot-check that agents still select this tool as intended.
    Declared effect
    read → read
    Description
    PreviousFetch 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 (origin overridable via the LUXALGO_APP_ORIGIN env var). 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.
    CurrentFetch 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.

    Input schema

    Input schema unchanged.

    3 unchanged entries
    • (schema root)
    • challengeId
    • firmId

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  7. propfirms_list_simulatableModifiedDescriptionINFO

    What changed

    • propfirms_list_simulatable: description changed.

    Why it could matter

    • Models choose and call tools partly from their descriptions.

    What to verify

    • Spot-check that agents still select this tool as intended.
    Declared effect
    read → read
    Description
    PreviousList 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 (origin overridable via the LUXALGO_APP_ORIGIN env var). 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.
    CurrentList 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.

    Input schema

    Input schema unchanged.

    2 unchanged entries
    • (schema root)
    • productType

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  8. propfirms_optimal_riskModifiedDescriptionINFO

    What changed

    • propfirms_optimal_risk: description changed.

    Why it could matter

    • Models choose and call tools partly from their descriptions.

    What to verify

    • Spot-check that agents still select this tool as intended.
    Declared effect
    read → read
    Description
    PreviousSweep 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.
    CurrentSweep 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.

    Input schema

    Input schema unchanged.

    79 unchanged entries
    • (schema root)
    • attemptCap
    • avgLossR
    • avgWinR
    • challengeId
    • firmId
    • fundedHorizonDays
    • lossStdR
    • max
    • min
    • paths
    • riskMode
    • seed
    • simulateFunded
    • spec
    • spec › accountSize
    • spec › challengeId
    • spec › constraints
    • spec › currency
    • spec › dailyLoss
    • spec › fees
    • spec › fees › activationFee
    • spec › fees › billing
    • spec › fees › price
    • spec › fees › refundableOnPass
    • spec › fees › resetFee
    • spec › flagsNotSimulated
    • spec › flagsNotSimulated › [items]
    • spec › funded
    • spec › funded › dailyLoss
    • spec › funded › firstPayoutMinDays
    • spec › funded › maxLoss
    • spec › funded › maxLoss › amount
    • spec › funded › maxLoss › lockOffsetAmount
    • spec › funded › maxLoss › locksAtInitial
    • spec › funded › maxLoss › mode
    • spec › funded › maxLoss › pct
    • spec › funded › notes
    • spec › funded › payoutFrequency
    • spec › funded › payoutRules
    • spec › funded › payoutRules › bufferAmount
    • spec › funded › payoutRules › consistencyMaxBestDayPct
    • spec › funded › payoutRules › maxPayoutAmount
    • spec › funded › payoutRules › maxPayoutPctOfProfit
    • spec › funded › payoutRules › minWinningDays
    • spec › funded › payoutRules › winningDayMinProfit
    • spec › funded › profitSplitPct
    • spec › maxLoss
    • spec › maxLoss › amount
    • spec › maxLoss › lockOffsetAmount
    • spec › maxLoss › locksAtInitial
    • spec › maxLoss › mode
    • spec › maxLoss › pct
    • spec › name
    • spec › productType
    • spec › sources
    • spec › sources › [items]
    • spec › sources › [items] › lastVerified
    • spec › sources › [items] › note
    • spec › sources › [items] › url
    • spec › steps
    • spec › steps › [items]
    • spec › steps › [items] › consistency
    • spec › steps › [items] › dailyLoss
    • spec › steps › [items] › maxDays
    • spec › steps › [items] › maxLoss
    • spec › steps › [items] › maxLoss › amount
    • spec › steps › [items] › maxLoss › lockOffsetAmount
    • spec › steps › [items] › maxLoss › locksAtInitial
    • spec › steps › [items] › maxLoss › mode
    • spec › steps › [items] › maxLoss › pct
    • spec › steps › [items] › minTradingDays
    • spec › steps › [items] › profitTargetAmount
    • spec › steps › [items] › profitTargetPct
    • step
    • tradesPerDay
    • tradesPerDayModel
    • winRate
    • winStdR

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  9. propfirms_simulateModifiedDescriptionINFO

    What changed

    • propfirms_simulate: description changed.

    Why it could matter

    • Models choose and call tools partly from their descriptions.

    What to verify

    • Spot-check that agents still select this tool as intended.
    Declared effect
    read → read
    Description
    PreviousMonte 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 - a distinguishing feature of this engine. 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'). The pre-1.0 flag id 'funded-payout-resets-account' no longer exists. 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 (origin overridable via the LUXALGO_APP_ORIGIN env var). 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. Composes with any broker-statistics tool: if another MCP server exposes round-trip statistics (winRate, avgWin, avgLoss) or a raw R-multiple series from the user's real trades, feed them here to answer "given my actual trading, what are my odds on this challenge and what risk should I use?". Convert currency statistics to R-multiples by dividing by the average amount risked per trade: winRate stays a fraction, avgWinR = avgWin / avgRisk, avgLossR = |avgLoss| / avgRisk.
    CurrentMonte 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.

    Input schema

    Input schema unchanged.

    78 unchanged entries
    • (schema root)
    • attemptCap
    • avgLossR
    • avgWinR
    • challengeId
    • firmId
    • fundedHorizonDays
    • includeHistograms
    • lossStdR
    • paths
    • riskMode
    • riskValue
    • seed
    • simulateFunded
    • spec
    • spec › accountSize
    • spec › challengeId
    • spec › constraints
    • spec › currency
    • spec › dailyLoss
    • spec › fees
    • spec › fees › activationFee
    • spec › fees › billing
    • spec › fees › price
    • spec › fees › refundableOnPass
    • spec › fees › resetFee
    • spec › flagsNotSimulated
    • spec › flagsNotSimulated › [items]
    • spec › funded
    • spec › funded › dailyLoss
    • spec › funded › firstPayoutMinDays
    • spec › funded › maxLoss
    • spec › funded › maxLoss › amount
    • spec › funded › maxLoss › lockOffsetAmount
    • spec › funded › maxLoss › locksAtInitial
    • spec › funded › maxLoss › mode
    • spec › funded › maxLoss › pct
    • spec › funded › notes
    • spec › funded › payoutFrequency
    • spec › funded › payoutRules
    • spec › funded › payoutRules › bufferAmount
    • spec › funded › payoutRules › consistencyMaxBestDayPct
    • spec › funded › payoutRules › maxPayoutAmount
    • spec › funded › payoutRules › maxPayoutPctOfProfit
    • spec › funded › payoutRules › minWinningDays
    • spec › funded › payoutRules › winningDayMinProfit
    • spec › funded › profitSplitPct
    • spec › maxLoss
    • spec › maxLoss › amount
    • spec › maxLoss › lockOffsetAmount
    • spec › maxLoss › locksAtInitial
    • spec › maxLoss › mode
    • spec › maxLoss › pct
    • spec › name
    • spec › productType
    • spec › sources
    • spec › sources › [items]
    • spec › sources › [items] › lastVerified
    • spec › sources › [items] › note
    • spec › sources › [items] › url
    • spec › steps
    • spec › steps › [items]
    • spec › steps › [items] › consistency
    • spec › steps › [items] › dailyLoss
    • spec › steps › [items] › maxDays
    • spec › steps › [items] › maxLoss
    • spec › steps › [items] › maxLoss › amount
    • spec › steps › [items] › maxLoss › lockOffsetAmount
    • spec › steps › [items] › maxLoss › locksAtInitial
    • spec › steps › [items] › maxLoss › mode
    • spec › steps › [items] › maxLoss › pct
    • spec › steps › [items] › minTradingDays
    • spec › steps › [items] › profitTargetAmount
    • spec › steps › [items] › profitTargetPct
    • tradesPerDay
    • tradesPerDayModel
    • winRate
    • winStdR

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  10. propfirms_simulate_tradesModifiedDescriptionINFO

    What changed

    • propfirms_simulate_trades: description changed.

    Why it could matter

    • Models choose and call tools partly from their descriptions.

    What to verify

    • Spot-check that agents still select this tool as intended.
    Declared effect
    read → read
    Description
    PreviousSimulate a challenge by resampling the trader's OWN R-multiple trade series with a stationary block bootstrap instead of a win-rate model. WHY THIS BEATS WIN-RATE MATH: 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 - a distinguishing feature of this engine. 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'). The pre-1.0 flag id 'funded-payout-resets-account' no longer exists. 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. Composes with any broker-statistics tool: if another MCP server exposes round-trip statistics (winRate, avgWin, avgLoss) or a raw R-multiple series from the user's real trades, feed them here to answer "given my actual trading, what are my odds on this challenge and what risk should I use?". Convert currency statistics to R-multiples by dividing by the average amount risked per trade: winRate stays a fraction, avgWinR = avgWin / avgRisk, avgLossR = |avgLoss| / avgRisk.
    CurrentSimulate 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.

    Input schema

    Input schema unchanged.

    90 unchanged entries
    • (schema root)
    • attemptCap
    • blockMeanLength
    • challengeId
    • firmId
    • fundedHorizonDays
    • importRisk
    • includeHistograms
    • newsFilter
    • newsFilter › currencies
    • newsFilter › currencies › [items]
    • newsFilter › customEventTimes
    • newsFilter › customEventTimes › [items]
    • newsFilter › impacts
    • newsFilter › impacts › [items]
    • newsFilter › postMinutes
    • newsFilter › preMinutes
    • paths
    • rSeries
    • rSeries › [items]
    • rSeriesText
    • riskMode
    • riskValue
    • seed
    • simulateFunded
    • spec
    • spec › accountSize
    • spec › challengeId
    • spec › constraints
    • spec › currency
    • spec › dailyLoss
    • spec › fees
    • spec › fees › activationFee
    • spec › fees › billing
    • spec › fees › price
    • spec › fees › refundableOnPass
    • spec › fees › resetFee
    • spec › flagsNotSimulated
    • spec › flagsNotSimulated › [items]
    • spec › funded
    • spec › funded › dailyLoss
    • spec › funded › firstPayoutMinDays
    • spec › funded › maxLoss
    • spec › funded › maxLoss › amount
    • spec › funded › maxLoss › lockOffsetAmount
    • spec › funded › maxLoss › locksAtInitial
    • spec › funded › maxLoss › mode
    • spec › funded › maxLoss › pct
    • spec › funded › notes
    • spec › funded › payoutFrequency
    • spec › funded › payoutRules
    • spec › funded › payoutRules › bufferAmount
    • spec › funded › payoutRules › consistencyMaxBestDayPct
    • spec › funded › payoutRules › maxPayoutAmount
    • spec › funded › payoutRules › maxPayoutPctOfProfit
    • spec › funded › payoutRules › minWinningDays
    • spec › funded › payoutRules › winningDayMinProfit
    • spec › funded › profitSplitPct
    • spec › maxLoss
    • spec › maxLoss › amount
    • spec › maxLoss › lockOffsetAmount
    • spec › maxLoss › locksAtInitial
    • spec › maxLoss › mode
    • spec › maxLoss › pct
    • spec › name
    • spec › productType
    • spec › sources
    • spec › sources › [items]
    • spec › sources › [items] › lastVerified
    • spec › sources › [items] › note
    • spec › sources › [items] › url
    • spec › steps
    • spec › steps › [items]
    • spec › steps › [items] › consistency
    • spec › steps › [items] › dailyLoss
    • spec › steps › [items] › maxDays
    • spec › steps › [items] › maxLoss
    • spec › steps › [items] › maxLoss › amount
    • spec › steps › [items] › maxLoss › lockOffsetAmount
    • spec › steps › [items] › maxLoss › locksAtInitial
    • spec › steps › [items] › maxLoss › mode
    • spec › steps › [items] › maxLoss › pct
    • spec › steps › [items] › minTradingDays
    • spec › steps › [items] › profitTargetAmount
    • spec › steps › [items] › profitTargetPct
    • tradeLogText
    • tradeLogTexts
    • tradeLogTexts › [items]
    • tradesPerDay
    • tradesPerDayModel

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  11. trackers_queryModifiedDescriptionINFO

    What changed

    • trackers_query: description changed.

    Why it could matter

    • Models choose and call tools partly from their descriptions.

    What to verify

    • Spot-check that agents still select this tool as intended.
    Declared effect
    read → read
    Description
    PreviousSearch 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 senator's trades → congress-trades, text 'Tuberville'; who lobbied on a bill → lobbying-filings, text 'H.R.1234'.
    CurrentSearch 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'.

    Input schema

    Input schema unchanged.

    12 unchanged entries
    • (schema root)
    • dataset
    • limit
    • offset
    • since
    • sort
    • text
    • ticker
    • until
    • where
    • years
    • years › [items]

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
37 tools with no recorded change
  • broker_accounts
  • broker_positions
  • broker_refresh
  • broker_setup
  • broker_stats
  • broker_trades
  • edge_presets
  • edge_report
  • edge_symbols
  • journal_add_trade
  • journal_breakdown
  • journal_calendar
  • journal_get_day
  • journal_get_trade
  • journal_list_accounts
  • journal_list_tags
  • journal_list_trades
  • journal_overview
  • journal_search_notes
  • journal_update_trade
  • library_get_concept
  • library_get_family
  • library_get_indicator
  • library_get_source_code
  • library_list_families
  • library_search
  • luxalgo_account
  • propfirms_compare
  • propfirms_get
  • propfirms_pass_rates
  • propfirms_search
  • propfirms_search_challenges
  • propfirms_search_offers
  • propfirms_validate_strategy
  • trackers_datasets
  • trackers_latest
  • trackers_ticker

Evidence and provenance

Static findings
REVIEW from Modelara’s automated analysis of the two declared interfaces. A policy outcome, not a security rating or a runtime test.
Human review
Pending human review. No reviewer decision is recorded for this comparison.
Published evidence
Part of Valyd’s published data generation listed in valyd-data-source.json. Published records are not rewritten.
Show provenance and exact files
Comparison
luxalgo-mcp-server/1.5.0~2.0.0The published comparison identifier.
Analyzer
modelara v0.1.8Policy version not recorded.Analyzed Nov 17, 2026, 12:40 AM UTC.
Distribution
npm
Previous release
@luxalgo/mcp@1.5.048 tools · published by the registry Sep 24, 2026, 10:20 PM UTCArtifact integritysha512-+tx/M2odIKN4CctSjq1GaFSsFuXUpjyhRJ4/FQbTNKUElBHQ4Zh2tKwbFTQInNK1JmNw8YymgCjsF+XMxGZ+1w==Interface fingerprintsha256:3fb40928ace57867a6b9af376e96cc6cfead3ead871e3bc7e031ab6ff01f9d0cExact interface snapshot (JSON)
Current release
@luxalgo/mcp@2.0.047 tools · published by the registry Oct 25, 2026, 3:05 PM UTCArtifact integritysha512-VS3s4hzAjMSg1IIcZicUD2ON6hS3Bx8SFslzn09XiJfPiH0I1LYnYYcrfy5ySLRB4ejsv5R8MSUJFiKfnyIxhQ==Interface fingerprintsha256:361850d61a14925ce094cee9e562dcda438fb7a3fb1a0630ab478d1a8aef3b20Exact interface snapshot (JSON)

The integrity value or digest identifies the exact artifact that was inspected; it does not show that the package is safe. The interface fingerprint identifies the declared tools and schemas Modelara recorded for that release.

MODELARA ANALYSIS OUTPUT

Interface findings

Analyzed with Modelara v0.1.8 · Nov 17, 2026

Requires review

2 findings
  • library_list_tagsREVIEWRemoved

    Capability removed; a workflow may depend on it

    Authority
    READ—
  • library_list_indicatorsREVIEWChanged

    Input schema changed

    Show details
    • input property removed: tags
    • input property concept changed: description "Concept slug — o… → "Concept slug (from…
    • input property family changed: +description="Family key from li…
    Authority
    READREAD
    Authority unchanged

Informational

10 findings
  • journal_update_noteINFOChanged

    Description changed

    Authority
    DESTRUCTIVEDESTRUCTIVE
    Authority unchanged
  • journal_write_noteINFOChanged

    Description changed

    Authority
    WRITEWRITE
    Authority unchanged
  • library_list_conceptsINFOChanged

    Description changed

    Authority
    READREAD
    Authority unchanged
  • library_list_indicatorsINFOChanged

    Description changed

    Authority
    READREAD
    Authority unchanged
  • propfirms_challenge_rulesINFOChanged

    Description changed

    Authority
    READREAD
    Authority unchanged
  • propfirms_list_simulatableINFOChanged

    Description changed

    Authority
    READREAD
    Authority unchanged
  • propfirms_optimal_riskINFOChanged

    Description changed

    Authority
    READREAD
    Authority unchanged
  • propfirms_simulateINFOChanged

    Description changed

    Authority
    READREAD
    Authority unchanged
  • propfirms_simulate_tradesINFOChanged

    Description changed

    Authority
    READREAD
    Authority unchanged
  • trackers_queryINFOChanged

    Description changed

    Authority
    READREAD
    Authority unchanged
What do these results mean?
PASS
No policy-significant interface change detected.
REVIEW
Interface changes require inspection.
FAIL
A policy-significant change was detected.
INVALID
The comparison could not be evaluated reliably.
← Back to LuxAlgo MCP release history