Skip to main content
Glama

PerpMetric perpetuals data

Market snapshot / screener

get_markets
Read-onlyIdempotent

Current metrics for every market on one venue in one normalized schema: price, returns (1m-24h), funding (raw, hourly %, APR %), open interest USD and change, 24h volume, mark-oracle/index basis. Sort and filter server-side to get top movers, funding extremes or OI expansion without pulling the full universe. Returned as columns+rows to save tokens.

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": {
      "venue": "<venue>"
    },
    "name": "get_markets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
orderNoabs = largest absolute value first (both directions).desc
venueYesExchange. hyperliquid = Hyperliquid (Core + HIP-3), aster = Aster, lighter = Lighter.
sort_byNovolume_24h_usd
symbolsNoOptional: only these symbols (e.g. ["BTC","ETH"]).
market_setNoHyperliquid only: core perps or HIP-3 builder-deployed markets (e.g. xyz:TSLA). Ignored for other venues.core
min_volume_24h_usdNoDrop illiquid markets below this 24h USD volume.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The description adds two useful behavioral facts beyond that: results are normalized across venues into one schema, and the payload is returned as columns+rows for token efficiency. However, it says nothing about pagination/truncation behavior, whether limit is applied after filtering, or how missing metrics are represented.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each doing distinct work: schema contents, usage pattern, and return format. The metric enumeration is front-loaded with the resource, and the server-side sorting point is placed before the token-savings rationale. No filler or restatement of the title.

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 no output schema, the description correctly takes on the burden of describing the return shape (columns+rows) and the field set, and it covers venue scope and server-side sort/filter. It is nearly complete for a screener. Minor gaps remain around default row count behavior, treatment of null/absent metrics, and any rate or payload-size limits.

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 coverage is 71% with enums and per-parameter descriptions for venue, market_set, symbols, order and min_volume, so the schema already does most of the work. The description contributes context about what the sortable metric columns mean (e.g. funding as raw, hourly %, APR %; basis in bps), which helps interpret sort_by values, but it does not explain limit semantics or the interaction between filtering and the row cap. Baseline 3 is appropriate given the moderate coverage.

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 the resource (every market on one venue) and enumerates the returned metrics: price, multi-window returns, funding in three representations, OI USD and change, 24h volume, and mark-oracle/index basis. It also states the normalization guarantee across venues, which is a real distinguishing trait. It stops short of explicitly contrasting with siblings such as explain_market or compare_venues, leaving the agent to infer that this is the bulk screener rather than the explainer or cross-venue view.

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 gives concrete use cases — top movers, funding extremes, OI expansion — and states the key operational posture that sorting/filtering happens server-side so the full universe needn't be pulled. That is genuine when-to-use guidance. It offers no explicit when-not-use or named alternative, so an agent could still hesitate between this and find_funding_spreads for the 'funding extremes' case.

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