Skip to main content
Glama
This connector has been deprecated

This connector has been replaced by OptimistFi, the same server under its official MCP Registry name com.optimistfi/optimistfi.

Prop firms: crypto perps and CME futures

get_prop_firms
Read-onlyIdempotent

Prop firms for crypto perps and CME futures (Topstep, Apex), from their own pages: rules, prices, live codes, payout rules, country, platforms; a firm's on-chain book. Use when the user asks: prop firm rules; X promo code; Topstep payout rules; cheapest $50K challenge. Args: firm; market; rule; account_usd; country; asset; on_chain; max_price_usd.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_prop_firms"
  }
}

Input Schema

NameRequiredDescriptionDefault
firmNoOne firm by name (Breakout, HyroTrader, Propr): its full record, every challenge and its dated rule changes. Unset: a short record per firm.
ruleNoOnly firms on one of OptimistFi's rule lists, by its slug.
assetNoOnly firms that offer this asset class.
marketNocrypto: firms that fund crypto (and stock) perps traders. futures: firms that fund CME futures traders (Topstep, Apex Trader Funding, My Funded Futures). Unset: both.
countryNoOnly firms based in this country: where the firm says it operates, else where its contracting company is registered (United Arab Emirates or UAE, United States or US, Cayman Islands).
on_chainNotrue: only firms whose trades execute on an on-chain venue.
account_usdNoOnly challenges of this account size in dollars (50000): each firm's challenges at that size, cheapest to get funded first (the price after any live code plus any fee due on passing), and the firm's offers that cover it.
max_price_usdNoOnly firms whose cheapest published evaluation costs this much or less, in dollars (100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / market
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "crypto",
      +        "futures"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "crypto: firms that fund crypto (and stock) perps traders. futures: firms that fund CME futures traders (Topstep, Apex Trader Funding, My Funded Futures). Unset: both.",
      +  "title": "Market"
      +}
    • changedInput schema / properties / rule / anyOf
      Previous value: -[
      -  {
      -    "enum": [
      -      "static-drawdown",
      -      "under-50",
      -      "instant-funding",
      -      "no-daily-loss-limit",
      -      "stock-perps",
      -      "hyperliquid",
      -      "200k-accounts",
      -      "us-traders",
      -      "no-minimum-days"
      -    ],
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "static-drawdown",
      +      "under-50",
      +      "instant-funding",
      +      "no-daily-loss-limit",
      +      "stock-perps",
      +      "hyperliquid",
      +      "200k-accounts",
      +      "us-traders",
      +      "no-minimum-days",
      +      "cheapest",
      +      "daily-payouts",
      +      "eod-drawdown",
      +      "no-activation-fee"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / account_usd / description
      Previous value: -"Only challenges of this account size in dollars (50000): each firm's challenges at that size, cheapest first, each with the price after any live code, and the firm's offers that cover it."New value: +"Only challenges of this account size in dollars (50000): each firm's challenges at that size, cheapest to get funded first (the price after any live code plus any fee due on passing), and the firm's offers that cover it."
  3. Changed7 schema fields changed
    • changedInput schema / properties / account_usd / description
      Previous value: -"Only challenges of this account size in dollars (50000): each firm's programs at that size, with their prices and rules."New value: +"Only challenges of this account size in dollars (50000): each firm's challenges at that size, cheapest first, each with the price after any live code, and the firm's offers that cover it."
    • addedInput schema / properties / asset
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "Crypto",
      +        "Stocks",
      +        "ETFs",
      +        "Indices",
      +        "Commodities",
      +        "Forex"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Only firms that offer this asset class.",
      +  "title": "Asset"
      +}
    • addedInput schema / properties / country
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Only firms based in this country: where the firm says it operates, else where its contracting company is registered (United Arab Emirates or UAE, United States or US, Cayman Islands).",
      +  "title": "Country"
      +}
    • changedInput schema / properties / firm / description
      Previous value: -"One firm by name (Breakout, HyroTrader, Propr); unset lists every firm."New value: +"One firm by name (Breakout, HyroTrader, Propr): its full record, every challenge and its dated rule changes. Unset: a short record per firm."
    • changedInput schema / properties / max_price_usd / description
      Previous value: -"Only firms whose cheapest published evaluation costs this much or less."New value: +"Only firms whose cheapest published evaluation costs this much or less, in dollars (100)."
    • changedInput schema / properties / rule / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "static-drawdown",
      +      "under-50",
      +      "instant-funding",
      +      "no-daily-loss-limit",
      +      "stock-perps",
      +      "hyperliquid",
      +      "200k-accounts",
      +      "us-traders",
      +      "no-minimum-days"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / rule / description
      Previous value: -"Only firms on one of the site's rule lists: static-drawdown, under-50, instant-funding, no-daily-loss-limit, stock-perps, hyperliquid, 200k-accounts, us-traders, no-minimum-days."New value: +"Only firms on one of OptimistFi's rule lists, by its slug."
  4. Changed2 schema fields changed
    • addedInput schema / properties / account_usd
      Added value: +{
      +  "anyOf": [
      +    {
      +      "minimum": 1,
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Only challenges of this account size in dollars (50000): each firm's programs at that size, with their prices and rules.",
      +  "title": "Account Usd"
      +}
    • changedInput schema / properties / rule / description
      Previous value: -"Only firms on one of the site's rule lists: static-drawdown, under-50, instant-funding, no-daily-loss-limit, stock-perps, hyperliquid, 200k-accounts."New value: +"Only firms on one of the site's rule lists: static-drawdown, under-50, instant-funding, no-daily-loss-limit, stock-perps, hyperliquid, 200k-accounts, us-traders, no-minimum-days."
  5. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds useful provenance ('from their own pages') and hints that a firm record can include dated rule changes and an on-chain book. It says nothing about data freshness, rate limits, or response shape, which is acceptable given the rich annotations but leaves behavioral context thin.

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?

Front-loaded with what the tool returns and then immediately with usage triggers; every clause is dense but purposeful. The closing 'Args: firm; market; rule; ...' enumeration is redundant with the schema and could be dropped, which is the only waste.

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 eight-parameter, all-optional query tool with no output schema, the description supplies the essential domain, the returned data categories, and concrete example intents. It does not explain how filters combine or what an unfiltered call returns (the schema covers that), but nothing critical for correct invocation is missing.

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 per-parameter semantics are fully documented in the schema itself (firm, rule, asset, market, country, on_chain, account_usd, max_price_usd all carry explanations). The description's trailing 'Args:' list merely repeats parameter names without adding interpretation, so the baseline 3 is correct.

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 resource (prop firms) with its two domains (crypto perps and CME futures) and enumerates the returned content: rules, prices, live codes, payout rules, country, platforms, and the on-chain book. Named examples (Topstep, Apex) anchor the scope and make it clearly distinct from siblings like get_perps or get_perps_desk, which concern trading data rather than firm terms.

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 'Use when the user asks:' clause gives four concrete trigger queries (prop firm rules, promo code, Topstep payout rules, cheapest $50K challenge), which is strong positive routing. It stops short of naming an exclusion or an alternative tool for adjacent questions, so it reaches 4 rather than 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources