Skip to main content
Glama

Delistings: contracts being wound down

delistings
Read-only

Perpetual contracts the exchanges are winding down, with the settlement or delisting date where the exchange gives one, 24h volume and the current hourly rate. An extreme funding rate on a contract being removed is a trap: the position gets settled at the exchange's price and liquidity is leaving. Source: exchange contract statuses and disappearance from the instrument list — observed in our data, not an exchange announcement.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the summary and links: 'en' (default) or 'ru'
limitNoRows, default 15
exchangeNoOnly this exchange

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

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint, so the description carries the rest — and it does add real behavioral context: the source is exchange contract statuses plus disappearance from the instrument list, explicitly 'observed in our data, not an exchange announcement'. That caveat about coverage/reliability is exactly the kind of thing an agent needs and cannot get from structured fields.

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 compact sentences, front-loaded with what the tool returns, followed by the interpretive warning and the provenance caveat. Dense but every clause contributes; the first sentence is somewhat overloaded with field lists.

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?

Return shape is covered by the output schema, so the description need only explain what the data is and how to read it — which it does, including the settlement-at-exchange-price risk and the provenance caveat. Nothing critical to calling it 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% with enums for lang and exchange, so the schema already fully documents filtering and limits. The description adds no parameter-level detail (e.g., whether limit applies pre- or post-filter), so the 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?

The definition names a specific resource and scope: perpetual contracts exchanges are winding down, plus the fields returned (settlement/delisting date, 24h volume, hourly rate). It is clearly distinct from funding-history or liquidation siblings, though it never explicitly names or contrasts an alternative such as settlement_calendar.

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 rather than stated: the 'extreme funding rate on a contract being removed is a trap' line tells the agent how to interpret results and why the data matters, but there is no explicit when-to-call-this-vs-something-else guidance or prerequisite.

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