Skip to main content
Glama

Get quant features

get_feature
Read-onlyIdempotent

Pre-computed quantitative features (returns, realized vol, z-scores, funding, OI deltas — the schema enumerates every valid feature_name). mode=snapshot for the latest value, mode=timeseries for history, mode=outliers for the top-N most extreme instruments in a universe (e.g. hl_top50). Instrument ids are bare Hyperliquid symbols (BTC, HYPE) or dex-prefixed HIP-3 symbols (xyz:TSLA) — exactly the symbol values scan_markets returns. A null value means no data for that instrument/feature, not an error. (Requires api:read.)

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": {
      "mode": "<mode>",
      "feature_name": "<feature_name>"
    },
    "name": "get_feature"
  }
}

Input Schema

NameRequiredDescriptionDefault
nNooutliers only
endNoISO 8601 (timeseries only)
modeYes
startNoISO 8601 (timeseries only)
universe_idNoREQUIRED for outliers
feature_nameYes
instrument_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / universe_id / description
      Added value: +"REQUIRED for outliers"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description adds genuinely non-obvious behavior: a null value means no data rather than an error, and the call requires api:read. That null-semantics note is exactly the kind of thing an agent would otherwise misread as a failure.

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?

One dense paragraph, front-loaded with what the tool serves, then mode behavior, then id format and the null caveat. The em-dash-heavy sentence is long but every clause carries distinct information; no filler.

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 a 7-parameter, three-mode tool with no output schema, the description covers mode selection, id formatting, null handling, and auth. The remaining gap is the shape of a timeseries/outliers response, which nothing else documents since there is no output schema.

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 only 57% and instrument_id has no schema description at all, so the description compensates by specifying the accepted id formats (bare Hyperliquid symbols like BTC/HYPE, or dex-prefixed HIP-3 symbols like xyz:TSLA) and tying them to scan_markets output. It also gives the mode semantics that the bare enum listing does not convey; start/end remain only lightly covered.

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 names a specific resource and its content families (returns, realized vol, z-scores, funding, OI deltas) and points to the schema for the full feature_name enumeration, which separates it from price/bar siblings like get_bars and get_prices. It lacks an explicit verb ('retrieve/get'), but the operation is unambiguous.

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 clearly delineates the three modes: snapshot for the latest value, timeseries for history, outliers for the top-N most extreme instruments in a universe, with a concrete universe example (hl_top50). It does not, however, tell the agent when to prefer this over raw-bar siblings such as get_bars, so no explicit alternative is named.

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