Skip to main content
Glama

Ledger events

get_ledger_events
Idempotent

Individual ledger rows with default tax classification: perp opens, closes, liquidations and funding (main account and subaccounts); spot and HIP-4 outcome buys and sells; vault deposits and withdrawals; staking rewards; HyperEVM swaps, protocol deposits, loans and liquidity positions; transfers; papertrade mints and staking; anything unrecognised, flagged for review. Filter by event type or venue. Without paid access, live wallets return the first 10 rows.

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

Input Schema

NameRequiredDescriptionDefault
typeNo
limitNo
venueNoVenue key: hl (perps), hip3:<dex> (e.g. hip3:xyz), spot, outcome (HIP-4 outcome markets), vault, staking, evm (HyperEVM), pt (papertrade), fork, core (deposits and transfers); a subaccount's venues are sub:<address>:<venue>
sampleNoReturn deterministic sample data instead of reading Hyperliquid
addressYesPublic Hyperliquid wallet address
tax_yearNoTax year. AU-2027 = Australia · FY 2026–27; AU-2026 = Australia · FY 2025–26; US-2026 = United States · 2026; US-2025 = United States · 2025; UK-2027 = United Kingdom · 2026–27; UK-2026 = United Kingdom · 2025–26; CA-2026 = Canada · 2026; CA-2025 = Canada · 2025; NZ-2027 = New Zealand · 2026–27; NZ-2026 = New Zealand · 2025–26; JP-2026 = Japan · 2026; JP-2025 = Japan · 2025; ES-2026 = Spain · 2026; ES-2025 = Spain · 2025. Defaults by jurisdiction: AU AU-2026, US US-2026, UK UK-2026, CA CA-2026, NZ NZ-2027, JP JP-2026, ES ES-2026.
save_walletNoWith a Trader or Accountant plan API key: add this wallet to the plan if it is not on it yet (uses one of the plan's 10 wallets or a client seat). Without it, a wallet not on the plan gets the preview and a note.
jurisdictionNoUsed when tax_year is not given. AU = 1 Jul–30 Jun; US, CA, JP and ES = calendar year; UK = 6 Apr–5 Apr; NZ = 1 Apr–31 MarAU
unlock_tokenNoUnlock token returned by buy_report (or the website after paying), for wallets bought without an API key
trade_history_csvNoOptional: the text of a trade history CSV the user exported from Hyperliquid (Trade History, Export as CSV). Hyperliquid's API serves only about a wallet's most recent 10,000 fills, so for very active wallets this adds the older trades; only trades the API didn't return are added. Nothing is stored.
trade_history_accountNoOptional: the subaccount address the trade history file belongs to (from coverage.subaccounts). Omit for the main account's file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / trade_history_account
      Added value: +{
      +  "description": "Optional: the subaccount address the trade history file belongs to (from coverage.subaccounts). Omit for the main account's file.",
      +  "pattern": "^0x[0-9a-fA-F]{40}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / trade_history_csv
      Added value: +{
      +  "description": "Optional: the text of a trade history CSV the user exported from Hyperliquid (Trade History, Export as CSV). Hyperliquid's API serves only about a wallet's most recent 10,000 fills, so for very active wallets this adds the older trades; only trades the API didn't return are added. Nothing is stored.",
      +  "maxLength": 4000000,
      +  "type": "string"
      +}
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "open",
      -  "loss",
      -  "liq",
      -  "gain",
      -  "queued",
      -  "funding",
      -  "mint",
      -  "stake",
      -  "stakepay",
      -  "spotbuy",
      -  "spotgain",
      -  "spotloss",
      -  "vaultin",
      -  "vaultgain",
      -  "vaultloss",
      -  "income",
      -  "airdrop",
      -  "xfer",
      -  "evmswap",
      -  "defiin",
      -  "defiout",
      -  "receive"
      -]New value: +[
      +  "open",
      +  "loss",
      +  "liq",
      +  "gain",
      +  "queued",
      +  "funding",
      +  "mint",
      +  "stake",
      +  "stakepay",
      +  "spotbuy",
      +  "spotgain",
      +  "spotloss",
      +  "vaultin",
      +  "vaultgain",
      +  "vaultloss",
      +  "income",
      +  "airdrop",
      +  "xfer",
      +  "evmswap",
      +  "defiin",
      +  "defiout",
      +  "receive",
      +  "loan",
      +  "unknown"
      +]
    • changedInput schema / properties / venue / description
      Previous value: -"Venue key: hl (perps), hip3:<dex> (e.g. hip3:xyz), spot, vault, staking, evm (HyperEVM), pt (papertrade), fork, core (deposits and transfers)"New value: +"Venue key: hl (perps), hip3:<dex> (e.g. hip3:xyz), spot, outcome (HIP-4 outcome markets), vault, staking, evm (HyperEVM), pt (papertrade), fork, core (deposits and transfers); a subaccount's venues are sub:<address>:<venue>"
  2. Changed4 schema fields changed
    • changedInput schema / properties / jurisdiction / description
      Previous value: -"Used when tax_year is not given. AU = 1 Jul–30 Jun; US and CA = calendar year; UK = 6 Apr–5 Apr; NZ = 1 Apr–31 Mar"New value: +"Used when tax_year is not given. AU = 1 Jul–30 Jun; US, CA, JP and ES = calendar year; UK = 6 Apr–5 Apr; NZ = 1 Apr–31 Mar"
    • changedInput schema / properties / jurisdiction / enum
      Previous value: -[
      -  "AU",
      -  "US",
      -  "UK",
      -  "CA",
      -  "NZ"
      -]New value: +[
      +  "AU",
      +  "US",
      +  "UK",
      +  "CA",
      +  "NZ",
      +  "JP",
      +  "ES"
      +]
    • changedInput schema / properties / tax_year / description
      Previous value: -"Tax year. AU-2027 = Australia · FY 2026–27; AU-2026 = Australia · FY 2025–26; US-2026 = United States · 2026; US-2025 = United States · 2025; UK-2027 = United Kingdom · 2026–27; UK-2026 = United Kingdom · 2025–26; CA-2026 = Canada · 2026; CA-2025 = Canada · 2025; NZ-2027 = New Zealand · 2026–27; NZ-2026 = New Zealand · 2025–26. Defaults by jurisdiction: AU AU-2026, US US-2026, UK UK-2026, CA CA-2026, NZ NZ-2027."New value: +"Tax year. AU-2027 = Australia · FY 2026–27; AU-2026 = Australia · FY 2025–26; US-2026 = United States · 2026; US-2025 = United States · 2025; UK-2027 = United Kingdom · 2026–27; UK-2026 = United Kingdom · 2025–26; CA-2026 = Canada · 2026; CA-2025 = Canada · 2025; NZ-2027 = New Zealand · 2026–27; NZ-2026 = New Zealand · 2025–26; JP-2026 = Japan · 2026; JP-2025 = Japan · 2025; ES-2026 = Spain · 2026; ES-2025 = Spain · 2025. Defaults by jurisdiction: AU AU-2026, US US-2026, UK UK-2026, CA CA-2026, NZ NZ-2027, JP JP-2026, ES ES-2026."
    • changedInput schema / properties / tax_year / enum
      Previous value: -[
      -  "AU-2027",
      -  "AU-2026",
      -  "US-2026",
      -  "US-2025",
      -  "UK-2027",
      -  "UK-2026",
      -  "CA-2026",
      -  "CA-2025",
      -  "NZ-2027",
      -  "NZ-2026"
      -]New value: +[
      +  "AU-2027",
      +  "AU-2026",
      +  "US-2026",
      +  "US-2025",
      +  "UK-2027",
      +  "UK-2026",
      +  "CA-2026",
      +  "CA-2025",
      +  "NZ-2027",
      +  "NZ-2026",
      +  "JP-2026",
      +  "JP-2025",
      +  "ES-2026",
      +  "ES-2025"
      +]
  3. Changed2 schema fields changed
    • addedInput schema / properties / save_wallet
      Added value: +{
      +  "default": false,
      +  "description": "With a Trader or Accountant plan API key: add this wallet to the plan if it is not on it yet (uses one of the plan's 10 wallets or a client seat). Without it, a wallet not on the plan gets the preview and a note.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / tax_year / description
      Previous value: -"Tax year. AU-2027 = Australia · FY 2026–27; AU-2026 = Australia · FY 2025–26; US-2026 = United States · 2026; US-2025 = United States · 2025; UK-2027 = United Kingdom · 2026–27; UK-2026 = United Kingdom · 2025–26; CA-2026 = Canada · 2026; CA-2025 = Canada · 2025; NZ-2027 = New Zealand · 2026–27; NZ-2026 = New Zealand · 2025–26. Defaults to the year being filed now."New value: +"Tax year. AU-2027 = Australia · FY 2026–27; AU-2026 = Australia · FY 2025–26; US-2026 = United States · 2026; US-2025 = United States · 2025; UK-2027 = United Kingdom · 2026–27; UK-2026 = United Kingdom · 2025–26; CA-2026 = Canada · 2026; CA-2025 = Canada · 2025; NZ-2027 = New Zealand · 2026–27; NZ-2026 = New Zealand · 2025–26. Defaults by jurisdiction: AU AU-2026, US US-2026, UK UK-2026, CA CA-2026, NZ NZ-2027."
  4. Changed1 schema field changed
    • changedInput schema / properties / venue / description
      Previous value: -"Venue key: hl (perps), hip3:<dex> (e.g. hip3:xyz), spot, vault, staking, evm (HyperEVM), pt (Papertrade), fork, core (deposits and transfers)"New value: +"Venue key: hl (perps), hip3:<dex> (e.g. hip3:xyz), spot, vault, staking, evm (HyperEVM), pt (papertrade), fork, core (deposits and transfers)"
  5. Changed4 schema fields changed
    • changedInput schema / properties / jurisdiction / description
      Previous value: -"Used when tax_year is not given. AU = financial year 1 Jul–30 Jun; US = calendar year"New value: +"Used when tax_year is not given. AU = 1 Jul–30 Jun; US and CA = calendar year; UK = 6 Apr–5 Apr; NZ = 1 Apr–31 Mar"
    • changedInput schema / properties / jurisdiction / enum
      Previous value: -[
      -  "AU",
      -  "US"
      -]New value: +[
      +  "AU",
      +  "US",
      +  "UK",
      +  "CA",
      +  "NZ"
      +]
    • changedInput schema / properties / tax_year / description
      Previous value: -"Tax year. AU-2027 = Australia · FY 2026–27; AU-2026 = Australia · FY 2025–26; US-2026 = United States · 2026; US-2025 = United States · 2025. Defaults to the year being filed now."New value: +"Tax year. AU-2027 = Australia · FY 2026–27; AU-2026 = Australia · FY 2025–26; US-2026 = United States · 2026; US-2025 = United States · 2025; UK-2027 = United Kingdom · 2026–27; UK-2026 = United Kingdom · 2025–26; CA-2026 = Canada · 2026; CA-2025 = Canada · 2025; NZ-2027 = New Zealand · 2026–27; NZ-2026 = New Zealand · 2025–26. Defaults to the year being filed now."
    • changedInput schema / properties / tax_year / enum
      Previous value: -[
      -  "AU-2027",
      -  "AU-2026",
      -  "US-2026",
      -  "US-2025"
      -]New value: +[
      +  "AU-2027",
      +  "AU-2026",
      +  "US-2026",
      +  "US-2025",
      +  "UK-2027",
      +  "UK-2026",
      +  "CA-2026",
      +  "CA-2025",
      +  "NZ-2027",
      +  "NZ-2026"
      +]
  6. Changed2 schema fields changed
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "open",
      -  "loss",
      -  "liq",
      -  "gain",
      -  "queued",
      -  "funding",
      -  "mint",
      -  "stake",
      -  "stakepay"
      -]New value: +[
      +  "open",
      +  "loss",
      +  "liq",
      +  "gain",
      +  "queued",
      +  "funding",
      +  "mint",
      +  "stake",
      +  "stakepay",
      +  "spotbuy",
      +  "spotgain",
      +  "spotloss",
      +  "vaultin",
      +  "vaultgain",
      +  "vaultloss",
      +  "income",
      +  "airdrop",
      +  "xfer",
      +  "evmswap",
      +  "defiin",
      +  "defiout",
      +  "receive"
      +]
    • changedInput schema / properties / venue / description
      Previous value: -"Venue key, e.g. hl, hip3:xyz, hip3:para, pt"New value: +"Venue key: hl (perps), hip3:<dex> (e.g. hip3:xyz), spot, vault, staking, evm (HyperEVM), pt (Papertrade), fork, core (deposits and transfers)"
  7. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The description adds useful behavior beyond annotations by disclosing the unpaid preview limit, default tax classification, and that unrecognised rows are flagged. It omits the mutation implied by save_wallet and does not clarify output structure, which matters given readOnlyHint=false.

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 description is front-loaded with the core resource definition and the access limitation is saved for the end. The long semicolon-separated enumeration is dense but purposeful for covering many event categories.

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?

For an 11-parameter tool with no output schema but rich parameter descriptions, this gives enough context to understand what is returned and how to filter it. It is slightly incomplete about the save_wallet side effect and pagination/limit behavior, though those are present in the schema.

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 high at 82%, so the schema already documents most parameters. The description reinforces filtering by type and venue but adds little detail on tax_year, jurisdiction, save_wallet, trade_history_csv, or limit beyond what the schema provides.

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 the resource as individual ledger rows with tax classification and enumerates the event categories covered, so an agent can tell it apart from summary/export siblings. It does not explicitly name sibling tools or contrasts, which keeps it from a 5.

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?

It says the result can be filtered by event type or venue and notes the unpaid-access limit, which gives some usage context. However, it does not say when to use this tool instead of get_tax_summary or export_tax_file, so routing guidance is only implied.

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