Skip to main content
Glama
Sign In

TradingAgentStack

by io.github.intoApex
OverviewDiscussionsAdmin

Look up one verified track record

get_track_record
Read-onlyIdempotent

Look up one verified track record by Hyperliquid vault address, vault URL or name, Lighter public pool index or URL, dHEDGE vault address, or the address of an AI agent whose operator published its Hyperliquid or Polymarket account: return, BTC over the same dates, max drawdown, Sortino, 30-day return and TVL (for Polymarket agents: ROI on money put in, PnL and win rate), computed by TradingAgentStack from Hyperliquid's public API (not self-reported), with the window, the data date, whether it passes the 30% drawdown gate and until when it is fresh, and a SHA-256 of the record so an agent can cite exactly what it read. On the hosted endpoint the hash also comes signed (an ES256 JWT whose public keys are published), so anyone can check later that TradingAgentStack issued that exact record. Unknown addresses come back as not_tracked with how to get verified. Not investment advice.

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": {
      "query": "<query>"
    },
    "name": "get_track_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesVault or agent account address (0x...), app.hyperliquid.xyz/vaults/ URL, or vault or agent name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Vault address (0x...), app.hyperliquid.xyz/vaults/ URL or vault name"New value: +"Vault or agent account address (0x...), app.hyperliquid.xyz/vaults/ URL, or vault or agent name"
  2. Added

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: it discloses the data provenance (computed from Hyperliquid's public API, not self-reported), the exact metric set including the Polymarket-specific ROI/PnL/win-rate variant, the drawdown gate, freshness window, and a SHA-256 integrity hash with an optional ES256 JWT signature whose public keys are published. The not_tracked failure mode is also spelled out, which annotations cannot convey.

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?

Purpose is correctly front-loaded, but the remainder is a single ~150-word run-on sentence that chains metric lists, provenance, integrity hashing, and a disclaimer. The content is largely worth keeping, yet it would read far better split into scope / returns / failure-mode sentences; 'Not investment advice' is boilerplate.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 carries the full burden of describing the return payload, and it does so field by field (return, BTC benchmark, max drawdown, Sortino, 30-day return, TVL, window, data date, gate status, hash, signature). For a single-parameter read tool this leaves no meaningful caller question unanswered.

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% and the schema itself only lists 0x addresses, Hyperliquid vault URLs, and names. The description meaningfully broadens that by adding Lighter public pool indices/URLs, dHEDGE vault addresses, and AI agent addresses, so an agent knows inputs the schema alone would reject as out of scope.

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 verb and resource ('Look up one verified track record') and enumerates exactly which identifier types resolve to a record: Hyperliquid vault address/URL/name, Lighter pool index/URL, dHEDGE vault address, or an agent account address. 'One' cleanly separates it from a bulk/leaderboard tool without needing to name one.

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 implied by 'one' (single-record lookup versus the leaderboard-style siblings) and it explains the unknown-input path ('Unknown addresses come back as not_tracked with how to get verified'). However, it never explicitly says when to prefer this over get_leaderboard or compare_tools, nor does it state prerequisites such as needing an address the operator has already published.

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

All TradingAgentStack 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