LuxAlgo MCP

Search prop-firm challenges

propfirms_search_challenges

Read-only

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.

Input Schema

Name	Required	Description
`sort`	No	Sort key (default accountSize descending)
`text`	No	Case-insensitive search over challenge name and firm name/slug
`steps`	No	Exact evaluation step count (1 = instant/funded, 2 = two-step, …)
`context`	Yes	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`	No	Pass ['offers'] to attach live offers that apply to each challenge
`interval`	No	Challenge fee intervals, e.g. 'one-time', 'monthly'
`priceMax`	No	Maximum challenge fee (inclusive)
`priceMin`	No	Minimum challenge fee (inclusive)
`stepsMax`	No	Maximum step count (ignored when steps is set)
`stepsMin`	No	Minimum step count (ignored when steps is set)
`direction`	No	Sort direction; each sort key has a sensible default
`pageIndex`	No	0-based page index (default 0)
`maxLossMax`	No	Upper bound on the overall-loss limit magnitude
`propfirmId`	No	Public firm slugs, e.g. ['ftmo']
`autoTrading`	No	Whether automated trading (EAs/bots) is allowed
`availableIn`	No	Country names the firm must NOT restrict, e.g. ['United States']
`challengeId`	No	Public challenge ids
`copyTrading`	No	Whether copy trading is allowed
`maxLossMode`	No	Drawdown modes; challenges without a captured mode never match
`newsTrading`	No	Whether news trading is allowed
`dailyLossMax`	No	Upper bound on the daily-loss limit magnitude (smaller = stricter)
`pageQuantity`	No	Page size (default 50, max 100)
`productTypes`	No	Product types the firm must offer at least one of, e.g. 'CFD', 'Futures'
`challengeName`	No	Case-insensitive substring of the challenge name
`accountSizeMax`	No	Maximum account size (inclusive)
`accountSizeMin`	No	Minimum account size (inclusive)
`maxLeverageMin`	No	Minimum max leverage
`profitSplitMin`	No	Minimum trader profit-split percent
`weekendHolding`	No	Whether holding over the weekend is allowed
`isFeeRefundable`	No	Whether the challenge fee is refundable
`overnightHolding`	No	Whether holding overnight is allowed
`stoplossRequired`	No	Whether a stop loss is required
`tradingPlatforms`	No	Platforms the firm must offer at least one of, e.g. 'MT5', 'cTrader', 'TradingView'
`minTradingDaysMax`	No	Maximum required minimum trading days (finds less-strict challenges)
`tradedMarketTypes`	No	Markets the firm must offer at least one of, e.g. 'forex', 'indices', 'commodities'
`isPreferredPartner`	No	Only LuxAlgo preferred-partner firms when true

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedSep 8, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedInput schema / properties / context / description

Previous value: -"Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\""New value: +"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.\""

addedInput schema / properties / pageIndex / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / steps / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / steps / minimum
```
Added value: +-9007199254740991
```
addedInput schema / properties / stepsMax / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / stepsMax / minimum
```
Added value: +-9007199254740991
```
addedInput schema / properties / stepsMin / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / stepsMin / minimum
```
Added value: +-9007199254740991
```

Changed3 schema fields changedAug 31, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / context

Added value: +{
+  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
+  "type": "string"
+}

addedInput schema / required
```
Added value: +[
+  "context"
+]
```

AddedAug 26, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/destructiveHint/openWorldHint, so the safety profile is covered. The description still adds non-obvious behavior: uncaptured (null) rule fields are omitted from results and never match filters, and include=['offers'] yields a deduplicated top-level offers list with per-challenge offerIds. Return format specifics (pagination shape) remain unstated, keeping this at a 4 rather than 5.

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?

Front-loaded with the core action and scope, then progressively adds filtering scope, id-routing, include behavior, and sibling routing. Every sentence carries distinct information; nothing is redundant with the schema or annotations.

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

Completeness4/5

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

For a 36-parameter tool with 100% schema coverage and read-only annotations but no output schema, the description does the heavy lifting on routing and the offers/null-filter contract. It reasonably states the tool returns rules and terms rather than outcomes. Missing only explicit return-shape/pagination detail.

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 description coverage is 100%, so the baseline is 3. The description lifts this by clarifying the include=['offers'] contract (deduplicated top-level list, offerIds cross-reference, firm-wide offers included) and the null-field filter behavior, which the schema's one-line parameter notes do not convey. Minor added value beyond schema, hence 4.

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?

States a specific verb+resource ("Search funded-account challenges across all visible prop firms") and immediately names the dimension of differentiation (rules/terms vs. outcomes). Siblings propfirms_search, propfirms_search_offers, propfirms_compare are distinguishable because this tool returns challenge rule/term records specifically.

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

Usage Guidelines5/5

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

Explicit routing: "Pass propfirmId to list one firm's challenges, or challengeId to fetch specific ones," and it names the exact alternatives for downstream steps (propfirms_simulate, propfirms_pass_rates, propfirms_validate_strategy) with the condition that selects each. When-to-use and when-to-go-elsewhere are both covered.

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

All LuxAlgo MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Search prop-firm challenges

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources