Skip to main content
Glama

Find pairs: by coin, exchange, side, rate or volume

pair_search
Read-only

Discover perpetual pairs on the radar: filter the scanner's 300 strongest pairs by coin or symbol substring, exchange, receiving side, minimum |hourly rate| or 24h volume; sort by rate, volume or open interest. Each row carries the rate in both forms, the receiving side, next settlement, volume, OI and the card link. A pair outside the 300 is reachable via pair_briefing by its exact symbol.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the summary and links: 'en' (default) or 'ru'
sortNoSort key, default rate (by |hourly rate|)
limitNoRows, default 10
queryNoCoin or symbol substring, case-insensitive (BTC, 1000PEPE, USDC)
exchangeNo
receiverNoWho receives funding: long (negative rate) or short (positive)
minVol24hUsdNoMinimum 24h volume in USD
minHourlyPercentNoMinimum |rate| in percent per hour, e.g. 0.05

Output Schema

NameRequiredDescriptionDefault
dataYesCompact numbers the conclusion is based on, units named inside
linkYesLive page with the same data
summaryYesOne-line conclusion — quote this

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / exchange / enum
      Previous value: -[
      -  "binance",
      -  "bybit",
      -  "okx",
      -  "bitget",
      -  "hyperliquid"
      -]New value: +[
      +  "binance",
      +  "bybit",
      +  "okx",
      +  "bitget",
      +  "hyperliquid",
      +  "gate",
      +  "aster",
      +  "bitunix"
      +]
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds real context beyond that, notably the hard 300-pair universe cap and the exact row contents (both rate forms, receiving side, next settlement, volume, OI, card link). It does not note any rate limits, auth, or truncation behavior when filters return many matches.

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?

Two dense sentences that are front-loaded with the verb and scope, with no filler or repetition of the schema. The first sentence is long and clause-heavy, packing all filter axes into one run-on list, but each clause carries distinct information.

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 an 8-optional-parameter, zero-required tool with an output schema, the definition covers the important unknowns: the 300-pair universe limit, filter axes, sort options, and the escape hatch to pair_briefing. What remains unstated (default sort/limit values, lang effect) is already documented in the 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 88%, so the baseline is 3, but the description adds interpretation: 'coin or symbol substring' clarifies query semantics, 'receiving side' ties to the long/short enum, and 'minimum |hourly rate|' plus 'sort by rate, volume or open interest' explain the absolute-value behavior behind two filters. It says nothing about lang or limit, which the schema covers on its own.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Discover perpetual pairs on the radar') plus a precise scope: the scanner's 300 strongest pairs. It also names the sibling it is not, pair_briefing, so an agent can separate the two without opening either schema.

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?

Gives an explicit routing rule for the out-of-scope case: a pair outside the 300 must go through pair_briefing by exact symbol. It does not explicitly say when to prefer this over spread_pairs, funding_events, or funding_history, so the broader when-to-use picture is left implicit.

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