Skip to main content
Glama
LuxAlgo

LuxAlgo Library MCP

Official
by LuxAlgo

Search prop firms

propfirms_search

Search and filter proprietary trading firms by platform, market, payment, country, and challenge criteria such as account size, profit split, and trading rules to find matching funded accounts.

Instructions

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort key (default name)
textNoCase-insensitive search over firm name and slug, e.g. 'ftmo'
stepsNoExact evaluation step count (1 = instant/funded, 2 = two-step, …)
includeNoExtra payloads to nest on each firm (only children matching the filters are returned)
offerIdNoPublic offer ids
currencyNoAccount currencies, e.g. ['usd', 'eur']
intervalNoChallenge fee intervals, e.g. 'one-time', 'monthly'
priceMaxNoMaximum challenge fee (inclusive)
priceMinNoMinimum challenge fee (inclusive)
stepsMaxNoMaximum step count (ignored when steps is set)
stepsMinNoMinimum step count (ignored when steps is set)
directionNoSort direction; each sort key has a sensible default
offerTextNoCase-insensitive search over promo code and offer descriptions
pageIndexNo0-based page index (default 0)
promoCodeNoCase-insensitive substring of the promo code
isFeaturedNoOnly featured offers when true
maxLossMaxNoUpper bound on the overall-loss limit magnitude
propfirmIdNoPublic firm slugs, e.g. ['ftmo']
autoTradingNoWhether automated trading (EAs/bots) is allowed
availableInNoCountry names the firm must NOT restrict, e.g. ['United States']
challengeIdNoPublic challenge ids
copyTradingNoWhether copy trading is allowed
countryIso2NoISO-2 headquarters countries, e.g. ['GB', 'US']
discountMaxNoMaximum discount value
discountMinNoMinimum discount value
maxLossModeNoDrawdown modes; challenges without a captured mode never match
newsTradingNoWhether news trading is allowed
dailyLossMaxNoUpper bound on the daily-loss limit magnitude (smaller = stricter)
pageQuantityNoPage size (default 50, max 100)
productTypesNoProduct types the firm must offer at least one of, e.g. 'CFD', 'Futures'
challengeNameNoCase-insensitive substring of the challenge name
payoutMethodsNoPayout methods the firm must offer at least one of, e.g. 'Bank Transfer', 'Crypto'
accountSizeMaxNoMaximum account size (inclusive)
accountSizeMinNoMinimum account size (inclusive)
hasActiveOfferNoWhen true, the firm must currently have a live (active, unexpired) offer
includeExpiredNoWhen true, ended offers are not hidden (default false)
maxLeverageMinNoMinimum max leverage
maxYearFoundedNoInclusive maximum year founded
minYearFoundedNoInclusive minimum year founded
paymentMethodsNoPayment methods the firm must accept at least one of, e.g. 'Crypto', 'PayPal'
profitSplitMinNoMinimum trader profit-split percent
weekendHoldingNoWhether holding over the weekend is allowed
includeInactiveNoWhen true, inactive offers are not hidden (default false)
isFeeRefundableNoWhether the challenge fee is refundable
overnightHoldingNoWhether holding overnight is allowed
stoplossRequiredNoWhether a stop loss is required
tradingPlatformsNoPlatforms the firm must offer at least one of, e.g. 'MT5', 'cTrader', 'TradingView'
discountIsPercentNotrue for percent discounts, false for absolute amounts
minTradingDaysMaxNoMaximum required minimum trading days (finds less-strict challenges)
tradedMarketTypesNoMarkets the firm must offer at least one of, e.g. 'forex', 'indices', 'commodities'
isPreferredPartnerNoOnly LuxAlgo preferred-partner firms when true
minTrustPilotCountNoMinimum Trustpilot review count
minTrustPilotScoreNoMinimum Trustpilot score

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so thoroughly: a firm matches only when at least one challenge/offer matches all filters, uncaptured null fields are omitted, nested challenges reference offers via offerIds into the firm-level offers list, and the data returned is explicitly directory data rather than simulation outcomes.

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

Conciseness5/5

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

The description is dense but well organized: core action and matching semantics first, then usage guidance, then result-shape caveats, then routing to outcome tools. Every sentence earns its place for a tool with 53 parameters and no annotations.

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

Completeness5/5

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

For a tool with 53 optional parameters and no output schema, the description covers matching semantics, null-omission behavior, nested payload behavior, the offerIds relationship, and explicit pointers to the dossier and simulation tools. An agent has enough information to select and call this tool correctly in the vast majority of cases.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents all 53 parameters. The description adds value by grouping parameters into firm, challenge, and offer filter categories and by explaining the critical 'at least one challenge/offer must match all filters' rule plus the include/offerIds wiring. It does not enumerate each parameter, but it does not need to given the rich schema.

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

Purpose5/5

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

The description opens with a specific verb and resource: 'Search LuxAlgo's prop-firm catalog', and defines what prop firms are. It distinguishes itself from propfirms_get ('for one firm's full dossier prefer propfirms_get') and from outcome-oriented tools by stating it returns directory data, not outcomes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear when-to-use guidance: omit all filters to list all firms, use include to nest matching challenges/offers/overview, and explicitly routes full-dossier and pass-odds use cases to propfirms_get and propfirms_pass_rates/propfirms_simulate. It does not, however, contrast this tool with the closely related propfirms_search_challenges and propfirms_search_offers siblings, leaving some alternative-selection to the agent.

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