LuxAlgo MCP

Search prop-firm offers

propfirms_search_offers

Read-only

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.

Input Schema

Name	Required	Description
`sort`	No	Sort key (default: featured first, then discount)
`text`	No	Case-insensitive search over promo code, descriptions, and firm name/slug
`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."
`offerId`	No	Public offer ids
`isActive`	No	Defaults to live offers only; pass false to look at inactive offers
`direction`	No	Sort direction; each sort key has a sensible default
`offerText`	No	Case-insensitive search over promo code and offer descriptions
`pageIndex`	No	0-based page index (default 0)
`promoCode`	No	Case-insensitive substring of the promo code
`isFeatured`	No	Only featured offers when true
`propfirmId`	No	Public firm slugs, e.g. ['ftmo']
`challengeId`	No	Public challenge ids; an offer matches when it applies to at least one (all-challenges offers match that firm's challenges)
`discountMax`	No	Maximum discount value
`discountMin`	No	Minimum discount value
`pageQuantity`	No	Page size (default 50, max 100)
`includeExpired`	No	When true, ended offers are not hidden (default false)
`includeInactive`	No	When true, inactive offers are not hidden (default false)
`discountIsPercent`	No	true for percent discounts, false for absolute amounts

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 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
```

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.1/5.0

Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so the safety bar is low; the description adds meaningful behavior by stating the live-offers default and enumerating the payload each offer carries (promo code, discount, end date, affiliate link). With no output schema, that return-field disclosure is genuinely useful. It does not cover pagination limits, but the schema does.

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

Conciseness4/5

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

Two densely informative sentences with the default behavior front-loaded and no filler. Slightly compressed—the challengeId clause is a bit parenthetical—but nothing is wasted.

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 an 18-parameter search with no output schema, the description covers intent, default scope, key routing filters, and return fields, which is close to complete. Remaining gaps (sorting, paging, the expire/inactive toggles) are handled adequately by the schema descriptions.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all 18 parameters, establishing a baseline of 3. The description's mention of propfirmId and challengeId filtering largely restates what the schema says (including the firm-wide offer inclusion note), adding little beyond it.

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 states a specific verb and resource ("Search promotional offers (discounts and promo codes) across prop firms") and scopes it to live offers by default. An agent can distinguish this from siblings like propfirms_search_challenges or propfirms_search, which cover different resources.

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?

It explains the default behavior (live/active, unexpired offers only) and how two key filters route the query (propfirmId narrows to one firm; challengeId resolves applicable offers including firm-wide ones). It stops short of naming alternatives such as propfirms_search_challenges or stating when-not to use this tool, so it is solid context without explicit exclusions.

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 offers

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources