Skip to main content
Glama

AINDEX

One Lighter RH market in detail

get_lighter_market
Read-only

One Lighter on Robinhood Chain market by symbol (NVDA, BTC, NVDA/USDG) or market id: mark and index price, 24h range, volume and trades, open interest, margin requirements, the last 24 hours of hourly funding, and the same symbol's funding on Binance, Bybit and Hyperliquid as Lighter reports them.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_lighter_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries the payload burden and does so well: it enumerates mark/index price, 24h range, volume and trades, open interest, margin requirements, 24h hourly funding, plus cross-venue funding from Binance, Bybit and Hyperliquid. That cross-venue comparison is real behavioral context an agent could not infer. It stops short of noting error behavior for unknown symbols.

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 front-loaded sentence opens with the purpose and then lists the returned fields, with no filler. It is dense but every clause identifies distinct payload content; slightly tighter punctuation grouping would improve scanability.

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 compensates by enumerating the return payload, which is exactly what an agent needs here. Given a one-parameter read tool with annotations covering the safety profile, the only real gap is behavior on invalid or unmatched symbols.

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 0% and the single parameter has only a regex pattern, so the description must explain it — and it does, giving accepted forms (NVDA, BTC, NVDA/USDG) and the numeric market-id alternative. This meaningfully exceeds the raw pattern, though it does not say whether a bare numeric string is always an id versus sometimes a ticker.

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 scope: a single Lighter market on Robinhood Chain, keyed by symbol or market id. That singular framing contrasted with the sibling get_lighter_markets is enough to tell them apart, though the distinction is implied 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 only implied by the singular 'One ... market' phrasing; there is no explicit 'use this when you need detail on a single market, use get_lighter_markets for a list'. No prerequisites, exclusions, or alternative routing are given.

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