Skip to main content
Glama
Sign In
traivo-mcp

traivo-mcp

Official
by traivoxyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Crypto perp markets

get_crypto_markets
Read-onlyIdempotent

Retrieves major crypto perpetual markets from Hyperliquid sorted by 24h volume with mid price, 24h change, volume, annualized funding, open interest, and max leverage.

Instructions

Major crypto perpetual markets from Hyperliquid, sorted by 24h volume as Traivo shows them: mid price, 24h change %, 24h volume (USD), annualised funding % and open interest (USD), max leverage. Reference data for majors; these are not Ethereum swaps.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to return (default 40, max 100).
symbolsNoOnly return these symbols. Omit for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: the upstream source (Hyperliquid), the sort order (24h volume desc), and — since there is no output schema — the exact fields returned.

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?

One dense front-loaded sentence carrying source, sort order and return fields, followed by a single short disambiguating clause. No filler and nothing buried.

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 two-optional-param list tool with no output schema, the description covers the source, ordering, and returned metrics an agent needs to interpret results. Minor gaps remain around what qualifies as a 'major' and how the list is bounded, but the schema handles the rest.

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 100%: both 'limit' (default 40, max 100) and 'symbols' (ticker format, case-insensitive, omit for all) are fully documented in the schema. The description adds no filtering or formatting detail beyond that, so baseline 3 applies.

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?

States a specific resource and scope: 'Major crypto perpetual markets from Hyperliquid, sorted by 24h volume', plus the exact metrics returned (mid price, 24h change, volume, funding, OI, max leverage). It only partially differentiates from siblings, negating 'Ethereum swaps' without naming get_onchain_tokens as the alternative.

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?

'Reference data for majors; these are not Ethereum swaps' implies a use case and one exclusion, but never names the sibling tool to use for swap/on-chain token data. There is no guidance on when a per-symbol lookup versus the full list is appropriate.

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

Deploy Server

Other Tools