Skip to main content
Glama

AINDEX

Lighter RH perps and spot markets

get_lighter_markets
Read-only

Every market on Lighter on Robinhood Chain (stock, ETF, commodity and crypto perps, and stock spot pairs against USDG): mark price, 24h move and volume, open interest, the latest funding (paid hourly; positive means longs pay shorts) and the same rate held for a year, max leverage and the smallest order. Filter by kind, sort by volume, funding (largest either way), open interest or the 24h move. Read only; cached a minute.

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_lighter_markets"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
sortNovolume
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the bar is lower, yet the description still adds genuine behavioral context: 'Read only; cached a minute' discloses staleness/freshness, and the definition of funding ('paid hourly; positive means longs pay shorts') and 'the same rate held for a year' explains how returned values should be interpreted. It does not discuss result size or truncation, which is the remaining behavioral gap.

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?

A single dense but well-ordered passage: scope first, then returned fields, then sort/filter capabilities, then read-only and caching caveats. Every clause carries information; it is packed but not padded. Slightly long for one breath, which keeps it off a 5.

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?

There is no output schema, and the description fully enumerates what comes back (mark price, 24h move, volume, open interest, funding, annualized rate, max leverage, smallest order), which is exactly what an agent needs. Missing only how many rows are returned by default and whether the list is paginated, a minor gap for a 3-param listing tool.

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 description coverage is 0%, so the description carries the burden. It adds real meaning beyond the schema for two of three parameters — 'funding (largest either way)' clarifies that funding sorting is by magnitude in both directions rather than descending signed value, and the kind enumeration is grounded in the market types. However, 'limit' is never mentioned (default 20, max 200 is left entirely to the schema), so compensation is partial.

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 specific resource and its full scope: 'Every market on Lighter on Robinhood Chain' with an explicit enumeration of instrument types (stock, ETF, commodity and crypto perps, plus stock spot pairs against USDG) and the fields returned. The word 'Every' signals bulk retrieval, which implicitly separates it from the singular sibling get_lighter_market, but that sibling is never named, so differentiation is inferred rather than stated.

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?

Usage is implied through 'Filter by kind, sort by volume, funding...' which tells the agent this is a screening/ranking tool, but there is no explicit statement of when to choose this over get_lighter_market or the other list_* market tools, and no exclusions. The agent can infer the discovery use case but must reason about the alternative itself.

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