Skip to main content
Glama

OptimistFi

by com.optimistfi.mcp
OverviewDiscussionsAdmin
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 for perpetual futures

get_prop_firms
Read-onlyIdempotent

Perps prop firms from their own pages: rules, challenge prices and live codes, country, platforms, assets, max allocation; a named firm's on-chain hedge book, reserves or payouts. Use when the user asks: prop firm rules; X discount code; cheapest $50K challenge; can Propr pay. Args: firm; rule; account_usd; country; asset; on_chain; max_price_usd.

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.
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. 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."
  2. 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."
  3. 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."
  4. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds mild provenance context ('from their own pages', implying self-reported/scraped data), but says nothing about freshness, caching, or coverage limits. With annotations carrying the load, a 3 is fair.

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

Conciseness3/5

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

Front-loaded with the data scope and use cases, which is good, but the prose is a semicolon run-on and the final Args list is pure duplication of a schema that is already 100% documented. Trimming that list would lose nothing.

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?

There is no output schema, so the description has to sketch the return content; it does (rules, challenge prices, codes, country, platforms, assets, max allocation, on-chain hedge book/reserves/payouts). With 7 optional params, all documented in the schema, and annotations covering the safety profile, an agent has enough to invoke it correctly.

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 the schema descriptions are rich (e.g., firm, account_usd, country all explain behavior in detail). The trailing 'Args: firm; rule; account_usd; country; asset; on_chain; max_price_usd.' merely repeats parameter names and adds no semantics beyond the schema. Baseline 3 is correct.

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 verb+resource: retrieves prop firm records (rules, challenge prices, live codes, country, platforms, assets) plus a named firm's on-chain hedge book, reserves or payouts. This is clearly distinct from the perps market/desk/history siblings. It stops short of naming those siblings, so an agent must infer the boundary from the noun alone.

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?

Gives concrete trigger utterances: 'prop firm rules', 'X discount code', 'cheapest $50K challenge', 'can Propr pay'. That is strong positive routing. There is no when-not guidance or explicit alternative (e.g., get_perps_market for exchange-side perp data), which keeps it out of 5 territory.

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

All OptimistFi toolsInspect
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