Skip to main content
Glama

Event history of a pair: does it repeat

pair_events
Read-only

How often one pair has had extreme funding (|rate| ≥ 0.1%/h) over 30 days, 7 days and 24 hours, how long an episode usually lasts, whether one is running now, and how past ones ended: funding accrued vs the price move against the receiving side. Counts episodes, not raw detector events (same-side events under an hour apart are merged). Answers whether a burning rate is a pattern or a one-off. Accepts an exact symbol (BTCUSDT) or just the coin (BTC).

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the summary and links: 'en' (default) or 'ru'
symbolYesNative pair symbol (BTCUSDT, BTC-USDT-SWAP) or base coin (BTC)
exchangeYesExchange id

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. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond readOnlyHint=true, the description discloses the threshold that defines an extreme rate (|rate| ≥ 0.1%/h), the aggregation rule that merges same-side events within an hour, and the shape of the answer including current-episode status. These are non-obvious behavioral traits an agent could not infer from the annotations or schema.

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?

The analytical content is front-loaded and the three sentences are dense but purposeful, with no filler. The trailing symbol-format sentence mildly duplicates the schema and could be dropped without loss.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and all three parameters fully described, the description carries only what structured fields cannot: the threshold definition, the episode-merging methodology, and the interpretive purpose. Nothing an agent needs to invoke or interpret this tool correctly is missing.

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 100%, so the schema already documents exchange, symbol, and lang, making 3 the baseline. The description's note that it accepts either an exact symbol or a bare coin largely restates the symbol field's own description rather than adding new meaning.

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?

The description names a specific resource (extreme funding episodes for one pair) with concrete measurement windows (30d/7d/24h), plus what it reports: episode duration, current state, and how past episodes resolved. It explicitly distinguishes its counting unit from raw detector events, so an agent can tell it apart from funding_events 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?

It frames the decision it answers ('whether a burning rate is a pattern or a one-off') and rules out the raw-event interpretation of the same data, which is strong contextual guidance. It does not name a sibling tool as the explicit alternative for that raw-event case, so it falls short of a full when/when-not routing statement.

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