FortFi Treasury MCP

backtest_copy_trade

Copy past test for any Hyperliquid address: replays the leader's own profit history over 7, 30 or 90 days at your leverage cap and account size, minus trading costs on their turnover. Returns end value, return, worst drop, costs, the leader's own numbers and an equity curve. An estimate from sampled history; read the assumptions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>"
    },
    "name": "backtest_copy_trade"
  }
}

Input Schema

Name	Required	Description
`days`	No	Default 30
`address`	Yes	0x Hyperliquid address
`costBps`	No	Fees plus price movement per traded dollar, basis points (default 10)
`leverageCap`	No	Your copy leverage cap (default 2)
`startEquityUsd`	No	Your starting account, USD (default 100)

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A3.8/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 does well: it discloses the simulation window (7/30/90 days), that the leader's history is replayed at the caller's leverage cap and account size, that trading costs are charged on the leader's turnover, and that the result is an estimate from sampled history. It stops short of stating outright that no orders are placed or funds touched, which is the one safety fact an agent would still want.

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?

Two dense sentences, front-loaded with the core purpose and followed by outputs and the caveat. Nothing is wasted, though the opening phrase 'Copy past test' is awkward and momentarily ambiguous.

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, and the description compensates by enumerating the return fields (end value, return, worst drop, costs, leader's numbers, equity curve). The only gap is the instruction to 'read the assumptions' without saying where those assumptions live.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns more by explaining what the parameters mean together — leverageCap and startEquityUsd define the simulated account, and costBps is applied to the leader's turnover rather than the caller's. Defaults and enum values stay with the schema, which is appropriate.

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 states a specific verb and resource ('replays the leader's own profit history' for 'any Hyperliquid address') and the name plus phrasing distinguish it from the live-trading siblings like start_copy_trade. It never names a sibling explicitly, so the backtest-vs-live-execution distinction has to be inferred from 'copy past test' and 'estimate'.

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?

Usage is only implied: 'an estimate from sampled history; read the assumptions' hints this is a pre-trade evaluation rather than execution. It gives no explicit when-to-use versus start_copy_trade or get_copy_trade_wallet, and no prerequisites or exclusions.

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

All FortFi Treasury MCP 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?