Skip to main content
Glama
Sign In

Tessera Analytics - Hyperliquid Market Intelligence

by dev.tesseralytics
OverviewDiscussionsAdmin

List fields

list_fields
Read-only

Every field the query tools accept, each with its meaning, unit, whether it can be missing, and which bars (1d, 1h) it exists on. Open — no key needed. Call this before query_cross_section, screen_universe or query_series. Percentile, z-score and the top_pct/bottom_pct conditions rank within the markets your plan can see, so they need a wide slice.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
notesYes
fieldsYesEvery field the query tools accept.
generated_atYesWhen this vocabulary was produced.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedOutput schema / $defs / FieldDoc / properties / best_horizon_hours
      Added value: +{
+  "description": "Horizon (hours) at which the field's signal is strongest/most durable.",
+  "format": "uint32",
+  "minimum": 0,
+  "nullable": true,
+  "type": "integer"
+}
    • addedOutput schema / $defs / FieldDoc / properties / class
      Added value: +{
+  "description": "Which signal class the field belongs to, when it has been measured:\n`state` (durable, 24 h horizon, retention ≈ 1), `microstructure`\n(same-bar, decays under the entry delay), `momentum` (short-term\nreversal that survives the delay) or `no_signal`. Absent for stored\ncolumns that were never measured on their own.",
+  "nullable": true,
+  "type": "string"
+}
    • addedOutput schema / $defs / FieldDoc / properties / delay_retention
      Added value: +{
+  "description": "Share of `ic_fwd` left when entry is delayed by the source's real\npublication lag (~2 h). Near 1 means durable; near 0 means same-bar only.",
+  "format": "double",
+  "nullable": true,
+  "type": "number"
+}
    • addedOutput schema / $defs / FieldDoc / properties / horizon_hours
      Added value: +{
+  "description": "Horizon (hours) at which `ic_fwd`, `ic_back` and `delay_retention` are\nstated.",
+  "format": "uint32",
+  "minimum": 0,
+  "nullable": true,
+  "type": "integer"
+}
    • addedOutput schema / $defs / FieldDoc / properties / ic_back
      Added value: +{
+  "description": "Backward-placebo IC at `horizon_hours`: large values mean the forward IC\nis partly contemporaneous with the return, not predictive of it.",
+  "format": "double",
+  "nullable": true,
+  "type": "number"
+}
    • addedOutput schema / $defs / FieldDoc / properties / ic_fwd
      Added value: +{
+  "description": "Forward cross-sectional rank IC at `horizon_hours`.",
+  "format": "double",
+  "nullable": true,
+  "type": "number"
+}
  2. Changed4 schema fields changed
    • addedOutput schema / $defs / FieldDoc / properties / grains
      Added value: +{
+  "description": "Plane grains on which this field is available, in canonical order.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedOutput schema / $defs / FieldDoc / properties / kind / description
      Previous value: -"`stored` (a column in the daily source) or `factor` (computed at query\ntime over a trailing window, or from the end-day row)."New value: +"`stored` (a column in the plane's own source) or `factor` (computed at\nquery time over a trailing window, or from the selected end row)."
    • changedOutput schema / $defs / FieldDoc / properties / nullable / description
      Previous value: -"Whether the value can be absent for a market on a day."New value: +"Whether the value can be absent for a market on a selected interval."
    • changedOutput schema / $defs / FieldDoc / required
      Previous value: -[
-  "name",
-  "meaning",
-  "unit",
-  "nullable",
-  "kind"
-]New value: +[
+  "name",
+  "meaning",
+  "unit",
+  "nullable",
+  "kind",
+  "grains"
+]
  3. Added

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description still adds genuine context beyond that: "Open — no key needed" documents the authentication requirement, and the note that percentile/z-score/top_pct conditions rank only within markets the plan can see discloses a data-scoping constraint. It does not cover rate limits or response size, so it is solid but not rich.

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?

Three sentences, front-loaded with what is returned, then when to call it, then a caveat. The final sentence about plan-scoped rankings is relevant but arrives without an explicit link to why it matters for choosing this tool, making it slightly loose.

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?

With zero parameters, an output schema present and readOnlyHint set, the remaining burden is small, and the description covers contents, prerequisites and call ordering. The one gap is that it never relates this catalog to the sibling dataset-description tools, leaving the agent to infer which reference tool to reach for.

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?

The tool takes zero parameters and the schema is empty, so there is nothing extra for the description to disambiguate. Baseline for a no-parameter tool applies.

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?

"Every field the query tools accept, each with its meaning, unit, whether it can be missing, and which bars (1d, 1h) it exists on" gives a precise verb-plus-resource with the exact contents of the response. An agent can distinguish this reference-catalog tool from describe_dataset, list_datasets and get_universe without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names three specific siblings to precede (query_cross_section, screen_universe, query_series), which is concrete when-to-use guidance. It stops short of stating exclusions — e.g. when to prefer describe_dataset or list_datasets instead — so the routing is not fully closed.

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

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