Tessera Analytics - Hyperliquid Market Intelligence

screen_universe

Screen the whole market on ONE completed interval with several conditions ANDed together. Pick bar (1d, the default, or 1h on a Pro key; a free key is screened at 1d). Conditions use op >, <, >=, <=, between, top_pct or bottom_pct; top_pct/bottom_pct are deciles of your eligible markets, and the liquidity floor is applied before the deciles so they are measured over the population you are choosing from. Answers 'top-decile funding with bottom-decile open-interest change' and 'open interest rising faster than volume'. A market that does not report a field never satisfies a condition on it.

Input Schema

TableJSON Schema

Name	Required	Description
`bar`	No	`1d` (the default) for completed UTC days, `1h` for completed UTC hours. An interval, at either grain, is stamped by the instant it closes — an hourly `…T09:00:00Z` is the hour that ended at 09:00.
`day`	No	The day or hour to screen: `YYYY-MM-DD` or `latest` at `bar: 1d`, a completed `YYYY-MM-DDTHH:00:00Z` (the hour that ended there) or `latest` at `bar: 1h`.
`coins`	No	Restrict to these markets.
`scope`	No	`crypto` (the default), `hip3`, or `all`.
`columns`	No	Fields to return per market, from `list_fields`.
`order_by`	No	The field to rank the matches by. Defaults to the interval's traded notional.
`conditions`	Yes	Conditions, all of which must hold. A market that does not report a field never satisfies a condition on it.
`descending`	No	Rank largest first (the default).
`max_results`	No	How many markets to return, 1..50. Defaults to 25.
`min_usd_volume_7d_avg`	No	Drop markets below this average daily traded notional over the window.

Output Schema

TableJSON Schema

Name	Required	Description
`bar`	Yes	The grain this answer was computed at: `1d` or `1h`.
`rows`	Yes
`as_of`	Yes
`notes`	Yes
`scope`	Yes
`source`	Yes
`row_count`	Yes
`truncated`	Yes
`matched_count`	Yes	Markets that met every condition.
`visible_count`	Yes	Markets in your plan's slice with a row on this interval, before any filter you passed.
`eligible_count`	Yes	Markets left after your explicit market filter and any traded-notional floor — the population the percentage conditions were measured against.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 14, 2026

addedInput schema / $defs / ConditionArg / properties / column / default
```
Added value: +null
```

changedInput schema / $defs / ConditionArg / properties / column / description

Previous value: -"The field to test, from `list_fields`."New value: +"The field to test, from `list_fields`. Accepted under either name —\n`field`, which is what every other argument on this surface calls it, or\nits original `column`. Validated as present rather than required by the\nschema, so a condition that names no field is rejected by name below\ninstead of by a deserializer message no caller can act on."

addedInput schema / $defs / ConditionArg / properties / column / nullable
```
Added value: +true
```

changedInput schema / $defs / ConditionArg / required

Previous value: -[
-  "column",
-  "op",
-  "value"
-]New value: +[
+  "op",
+  "value"
+]

Changed2 schema fields changedOct 8, 2026

changedInput schema / properties / bar / description

Previous value: -"`1d` (the default) for completed UTC days, `1h` for the most recent\ncompleted UTC hour."New value: +"`1d` (the default) for completed UTC days, `1h` for completed UTC hours.\nAn interval, at either grain, is stamped by the instant it **closes** —\nan hourly `…T09:00:00Z` is the hour that ended at 09:00."

changedInput schema / properties / day / description

Previous value: -"The day or hour to screen: `YYYY-MM-DD` or `latest` at `bar: 1d`, a\ncompleted `YYYY-MM-DDTHH:00:00Z` or `latest` at `bar: 1h`."New value: +"The day or hour to screen: `YYYY-MM-DD` or `latest` at `bar: 1d`, a\ncompleted `YYYY-MM-DDTHH:00:00Z` (the hour that *ended* there) or\n`latest` at `bar: 1h`."

Changed9 schema fields changedOct 2, 2026

addedInput schema / properties / bar

Added value: +{
+  "default": null,
+  "description": "`1d` (the default) for completed UTC days, `1h` for the most recent\ncompleted UTC hour.",
+  "nullable": true,
+  "type": "string"
+}

changedInput schema / properties / day / description

Previous value: -"The day to screen, `YYYY-MM-DD` or `latest`."New value: +"The day or hour to screen: `YYYY-MM-DD` or `latest` at `bar: 1d`, a\ncompleted `YYYY-MM-DDTHH:00:00Z` or `latest` at `bar: 1h`."

changedInput schema / properties / order_by / description

Previous value: -"The field to rank the matches by. Defaults to the day's traded notional."New value: +"The field to rank the matches by. Defaults to the interval's traded\nnotional."

addedOutput schema / properties / bar

Added value: +{
+  "description": "The grain this answer was computed at: `1d` or `1h`.",
+  "type": "string"
+}

removedOutput schema / properties / coin_count

Removed value: -{
-  "description": "The number of markets in your visible slice on that day — the\ndenominator the percentage conditions and the floor were measured\nagainst.",
-  "format": "int64",
-  "type": "integer"
-}

addedOutput schema / properties / eligible_count

Added value: +{
+  "description": "Markets left after your explicit market filter and any\ntraded-notional floor — the population the percentage conditions were\nmeasured against.",
+  "format": "int64",
+  "type": "integer"
+}

changedOutput schema / properties / matched_count / description

Previous value: -"How many markets met every condition."New value: +"Markets that met every condition."

addedOutput schema / properties / visible_count

Added value: +{
+  "description": "Markets in your plan's slice with a row on this interval, before any\nfilter you passed.",
+  "format": "int64",
+  "type": "integer"
+}

changedOutput schema / required

Previous value: -[
-  "source",
-  "as_of",
-  "scope",
-  "coin_count",
-  "matched_count",
-  "row_count",
-  "truncated",
-  "rows",
-  "notes"
-]New value: +[
+  "bar",
+  "source",
+  "as_of",
+  "scope",
+  "visible_count",
+  "eligible_count",
+  "matched_count",
+  "row_count",
+  "truncated",
+  "rows",
+  "notes"
+]

AddedSep 15, 2026

TDQS

Score is being calculated.

All Tessera Analytics - Hyperliquid Market Intelligence 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?