Skip to main content
Glama

Trade edge

trade_edge
Read-onlyIdempotent

All-in-one quantitative trading & risk package across 5 perp exchanges (Hyperliquid, Binance, Bybit, Bitget, Gate) and 10 blockchains (Ethereum, Base, Arbitrum, Optimism, Polygon, BNB, Solana, Arc, X1, Robinhood): delta-neutral funding carry spreads with exact fee breakeven hours, 10-chain exit-liquidity + MEV shield with Ed25519 receipt, and Quarter-Kelly / Risk-of-Ruin anti-tilt sizing. Free live radar: https://apexfaucet.xyz/trade/ . $0.005 per call over x402 or X-API-Key. Market data & math, not advice.

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": "trade_edge"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoQuant module to run (default: funding_arb).
chainNoBlockchain for token_armor (ethereum, base, arbitrum, optimism, polygon, bnb, solana, arc, x1, robinhood).
tokenNoToken contract/mint address for token_armor.
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).
win_rateNoOptional win rate (0.01-0.99 or 1-99) for kelly_discipline.
trade_usdNoProposed trade size in USD.
avg_win_pctNoOptional average win % for kelly_discipline.
capital_usdNoReference USD capital for carry & Kelly sizing (default 1000).
avg_loss_pctNoOptional average loss % for kelly_discipline.
drawdown_pctNoOptional current account drawdown % for anti-tilt circuit breaker.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the read-only, idempotent, and open-world annotations, it discloses a $0.005 per-call charge, x402/X-API-Key payment options, a live external radar, and the service's non-advice nature. Data freshness and sources, receipt semantics, and whether "MEV shield" is purely diagnostic remain unclear, though nothing directly conflicts with the annotations.

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?

The core capabilities are front-loaded, followed by concise pricing and disclaimer statements. The long venue/chain inventory and promotional "All-in-one" and radar wording make it denser than necessary, but its overall length is reasonable for a three-module tool.

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 three-mode, ten-parameter tool with no output schema, the description covers scope, conceptual results, cost, and payment sufficiently for a basic invocation. It does not explain returned structures or the receipt, clarify per-mode prerequisites and "all" behavior, or state how funding_arb chooses markets when no symbol or exchange parameter exists.

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 coverage is 100%, and the schema already documents modes, addresses, sizing inputs, defaults, and the payment payload. The description adds domain context and an X-API-Key alternative but largely repeats the chain inventory and does not clarify parameter dependencies or mode-specific input combinations.

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 identifies three concrete analytic functions: funding-carry spreads with fee breakeven, token exit-liquidity/MEV assessment, and Kelly/risk-of-ruin sizing. It also states venue and chain coverage, but does not explicitly distinguish the tool from overlapping siblings such as perp_funding or token_exit_matrix.

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?

The feature list implies when each module is useful, and "Market data & math, not advice" establishes a broad analytical boundary. However, there is no explicit mode-selection workflow, when-not guidance, or routing to narrower sibling tools when those would be preferable.

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