FirmFax prop firm data

find_firms

Firms matching every criterion given. A firm whose record does not carry a criterion is never counted as a match and never silently dropped: it is returned separately under unknown, with the field that could not be tested. Absence is common here, so read counts before treating the matched list as the answer.

Input Schema

TableJSON Schema

Name	Required	Description
`assetClass`	No	Firms recorded as offering this. 21 of 71 records name no asset class and are returned as unknown.
`maxResetFee`	No	Reset fee at or below this. 56 of 71 record no fee.
`maxActivationFee`	No	Activation fee at or below this. 42 of 71 record no fee.
`maxConsistencyPct`	No	Consistency rule at or below this. 28 of 71 record none.
`maxDailyLossLimit`	No	Daily loss limit at or below this, in the unit dailyLossLimitUnit names. 31 of 71 record none.
`maxMinTradingDays`	No	Minimum trading days at or below this, counted as minTradingDaysUnit names. 16 of 71 record none.
`dailyLossLimitUnit`	No	The unit maxDailyLossLimit is in. Daily loss limits are recorded in percent at some firms and in dollars at others, and the two are never compared: a firm recorded in the other unit is returned under unknown with its unit named.
`maxMinDaysToPayout`	No	Minimum days to first payout at or below this, counted as minDaysToPayoutUnit names. 26 of 71 record none.
`minTradingDaysUnit`	No	What maxMinTradingDays counts: calendar_days, trading_days or winning_days. A minimum is compared only with minimums counted the same way; a firm counting another way, or stating no unit, is returned under unknown with what it counts named.
`minDaysToPayoutUnit`	No	What maxMinDaysToPayout counts: calendar_days, trading_days or winning_days. A wait is compared only with waits counted the same way; a firm counting another way, or stating no unit, is returned under unknown with what it counts named.
`minTradingDaysMinProfit`	No	With winning_days only: the profit a day must reach to count. A firm whose winning days carry a different profit bar is returned under unknown.
`minDaysToPayoutMinProfit`	No	With winning_days only: the profit a day must reach to count. A firm whose winning days carry a different profit bar is returned under unknown.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 29, 2026

changedInput schema / properties / maxMinTradingDays / description

Previous value: -"Minimum trading days at or below this. 16 of 71 record none."New value: +"Minimum trading days at or below this, counted as minTradingDaysUnit names. 16 of 71 record none."

addedInput schema / properties / minTradingDaysMinProfit

Added value: +{
+  "description": "With winning_days only: the profit a day must reach to count. A firm whose winning days carry a different profit bar is returned under unknown.",
+  "type": "number"
+}

addedInput schema / properties / minTradingDaysUnit

Added value: +{
+  "description": "What maxMinTradingDays counts: calendar_days, trading_days or winning_days. A minimum is compared only with minimums counted the same way; a firm counting another way, or stating no unit, is returned under unknown with what it counts named.",
+  "enum": [
+    "calendar_days",
+    "trading_days",
+    "winning_days"
+  ],
+  "type": "string"
+}

Changed3 schema fields changedSep 25, 2026

changedInput schema / properties / maxMinDaysToPayout / description

Previous value: -"Minimum days to first payout at or below this. 26 of 71 record none."New value: +"Minimum days to first payout at or below this, counted as minDaysToPayoutUnit names. 26 of 71 record none."

addedInput schema / properties / minDaysToPayoutMinProfit

Added value: +{
+  "description": "With winning_days only: the profit a day must reach to count. A firm whose winning days carry a different profit bar is returned under unknown.",
+  "type": "number"
+}

addedInput schema / properties / minDaysToPayoutUnit

Added value: +{
+  "description": "What maxMinDaysToPayout counts: calendar_days, trading_days or winning_days. A wait is compared only with waits counted the same way; a firm counting another way, or stating no unit, is returned under unknown with what it counts named.",
+  "enum": [
+    "calendar_days",
+    "trading_days",
+    "winning_days"
+  ],
+  "type": "string"
+}

Changed2 schema fields changedSep 24, 2026

addedInput schema / properties / dailyLossLimitUnit

Added value: +{
+  "description": "The unit maxDailyLossLimit is in. Daily loss limits are recorded in percent at some firms and in dollars at others, and the two are never compared: a firm recorded in the other unit is returned under unknown with its unit named.",
+  "enum": [
+    "percent",
+    "usd"
+  ],
+  "type": "string"
+}

changedInput schema / properties / maxDailyLossLimit / description

Previous value: -"Daily loss limit at or below this. 31 of 71 record none."New value: +"Daily loss limit at or below this, in the unit dailyLossLimitUnit names. 31 of 71 record none."

AddedSep 13, 2026

TDQS

A3.6/5.0

Behavior4/5

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

With no annotations the description carries the full burden, and it delivers a genuinely useful behavioral trait not derivable from the schema alone: non-matching-by-absence records are returned separately under 'unknown' with the untestable field named, never silently dropped. It stops short of describing pagination, ordering, or the response envelope.

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?

Three sentences, front-loaded with the core predicate before the caveat, and each sentence carries distinct information. Minor density cost from the colon-and-clause construction, but no filler.

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

Completeness3/5

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

For a 12-parameter tool with no annotations and no output schema, the description covers the crucial unknown-bucket semantics but leaves the return shape, matched-list structure, and any limits unaddressed. Adequate but with an evident gap around what actually comes back.

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% and each parameter already documents its own unit and unknown-record counts (e.g. '56 of 71 record no fee'). The description adds no per-parameter syntax or semantics beyond what the schema provides, so the baseline 3 applies.

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

Purpose4/5

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

States a specific operation on a named resource: firms matching every criterion given, i.e. a conjunctive filter over firm records. That is clear enough to distinguish it from get_firm and compare_firms, though it never explicitly contrasts itself with list_firms, the nearest sibling.

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

Usage Guidelines3/5

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

Offers real interpretive guidance ('read counts before treating the matched list as the answer' because absence is common), but gives no explicit when-to-use/when-not-to-use framing and never routes the agent to compare_firms or list_firms. Usage is implied rather than stated.

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

All FirmFax prop firm data 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.

Resources

Need Help?