OptimistFi

This connector has been deprecated

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

Perps desk — news, traders and wallets

get_perps_desk

Read-onlyIdempotent

OptimistFi's perps desk: stories, traders with checked calls, wallets covered, companies that blocked tokenized trading of their stock, Kalshi's BTC/ETH odds and perp funding. Use when the user asks: perps news on X; is trader Y worth following; Kalshi's BTC odds. Args: view; market; trader; wallet; limit.

Input Schema

Name	Required	Description	Default
`dex`	No	account view only: Hyperliquid builder dex name, e.g. xyz; empty reads the main dex.
`view`	No	news: the desk's published perps stories, newest first. traders: the perps traders directory, with the desk's checked calls on each. wallets: the Hyperliquid wallets the desk has covered, with their stories. account: a fresh public Hyperliquid wallet state on one dex, with positions and margin; wallet is required. tokenized: which companies have blocked tokenized trading of their stock, from each venue's public notice. kalshi: Kalshi's BTC and ETH odds for the next 5 PM ET close and Friday's beside its perps' funding, read every five minutes, with its daily study of perps volume against open interest.	news
`limit`	No	Rows, up to 25.
`market`	No	news and traders: one market (BTC, NVDA, gold). tokenized: one company by ticker or name (MSFT, Microsoft). kalshi: BTC or ETH.
`trader`	No	traders: one trader by name or X handle.
`wallet`	No	wallets: one 0x address; adds what it holds now.
`max_age_s`	No	account only: maximum source age in seconds, default 3. A stale or undated account is unavailable.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 25, 2026

changedInput schema / properties / market / description

Previous value: -"news and traders: one market (BTC, NVDA, gold). tokenized: one company by ticker or name (MSFT, Microsoft)."New value: +"news and traders: one market (BTC, NVDA, gold). tokenized: one company by ticker or name (MSFT, Microsoft). kalshi: BTC or ETH."

changedInput schema / properties / view / description

Previous value: -"news: the desk's published perps stories, newest first. traders: the perps traders directory, with the desk's checked calls on each. wallets: the Hyperliquid wallets the desk has covered, with their stories. account: a fresh public Hyperliquid wallet state on one dex, with positions and margin; wallet is required. tokenized: which companies have blocked tokenized trading of their stock, from each venue's public notice."New value: +"news: the desk's published perps stories, newest first. traders: the perps traders directory, with the desk's checked calls on each. wallets: the Hyperliquid wallets the desk has covered, with their stories. account: a fresh public Hyperliquid wallet state on one dex, with positions and margin; wallet is required. tokenized: which companies have blocked tokenized trading of their stock, from each venue's public notice. kalshi: Kalshi's BTC and ETH odds for the next 5 PM ET close and Friday's beside its perps' funding, read every five minutes, with its daily study of perps volume against open interest."

changedInput schema / properties / view / enum

Previous value: -[
-  "news",
-  "traders",
-  "wallets",
-  "account",
-  "tokenized"
-]New value: +[
+  "news",
+  "traders",
+  "wallets",
+  "account",
+  "tokenized",
+  "kalshi"
+]

Changed3 schema fields changedOct 25, 2026

changedInput schema / properties / market / description

Previous value: -"news and traders: one market (BTC, NVDA, gold)."New value: +"news and traders: one market (BTC, NVDA, gold). tokenized: one company by ticker or name (MSFT, Microsoft)."

changedInput schema / properties / view / description

Previous value: -"news: the desk's published perps stories, newest first. traders: the perps traders directory, with the desk's checked calls on each. wallets: the Hyperliquid wallets the desk has covered, with their stories. account: a fresh public Hyperliquid wallet state on one dex, with positions and margin; wallet is required."New value: +"news: the desk's published perps stories, newest first. traders: the perps traders directory, with the desk's checked calls on each. wallets: the Hyperliquid wallets the desk has covered, with their stories. account: a fresh public Hyperliquid wallet state on one dex, with positions and margin; wallet is required. tokenized: which companies have blocked tokenized trading of their stock, from each venue's public notice."

changedInput schema / properties / view / enum

Previous value: -[
-  "news",
-  "traders",
-  "wallets",
-  "account"
-]New value: +[
+  "news",
+  "traders",
+  "wallets",
+  "account",
+  "tokenized"
+]

Changed4 schema fields changedOct 17, 2026

addedInput schema / properties / dex

Added value: +{
+  "default": "",
+  "description": "account view only: Hyperliquid builder dex name, e.g. xyz; empty reads the main dex.",
+  "title": "Dex",
+  "type": "string"
+}

addedInput schema / properties / max_age_s

Added value: +{
+  "default": 3,
+  "description": "account only: maximum source age in seconds, default 3. A stale or undated account is unavailable.",
+  "maximum": 30,
+  "minimum": 0.5,
+  "title": "Max Age S",
+  "type": "number"
+}

changedInput schema / properties / view / description

Previous value: -"news: the desk's published perps stories, newest first. traders: the perps traders directory, with the desk's checked calls on each. wallets: the Hyperliquid wallets the desk has covered, with their stories."New value: +"news: the desk's published perps stories, newest first. traders: the perps traders directory, with the desk's checked calls on each. wallets: the Hyperliquid wallets the desk has covered, with their stories. account: a fresh public Hyperliquid wallet state on one dex, with positions and margin; wallet is required."

changedInput schema / properties / view / enum

Previous value: -[
-  "news",
-  "traders",
-  "wallets"
-]New value: +[
+  "news",
+  "traders",
+  "wallets",
+  "account"
+]

AddedOct 12, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The annotations already cover the safety profile: readOnly, idempotent, non-destructive, open-world. The description adds some content-quality context such as 'traders with checked calls' and 'companies that blocked tokenized trading', but does not add much beyond the annotations and schema about freshness, caching, or response behavior.

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?

The description is reasonably front-loaded and compact, but the trailing 'Args: view; market; trader; wallet; limit' is redundant with the schema and incomplete because it omits dex and max_age_s. That sentence adds little value and slightly weakens precision.

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?

Given a seven-parameter, multi-view tool with no output schema, the description supplies useful intent examples and content categories. The rich schema and safe-read annotations fill most remaining gaps, though explicit differentiation from sibling perps tools and coverage of the account view would improve completeness.

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 every parameter is already documented in detail. The description only lists 'view; market; trader; wallet; limit' and omits dex and max_age_s, adding little meaning beyond the schema. Baseline 3 is appropriate when the schema carries parameter semantics.

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?

The description clearly identifies this as OptimistFi's perps desk and enumerates the content types it surfaces (stories, traders, wallets, tokenized stocks, Kalshi odds). However, it does not explicitly distinguish the tool from siblings such as get_perps, get_perps_market, or get_perps_history, leaving the agent to infer when this multi-view desk tool is preferable.

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 provides concrete example queries — perps news on X, whether trader Y is worth following, and Kalshi BTC odds — which clearly map user intent to this tool. It lacks explicit when-not-to-use guidance or named alternatives, but the usage context is strong.

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

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