Skip to main content
Glama
Sign In
MCP-Coinglass

MCP-Coinglass

by GPSxtreme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

COINGLASS_LONG_SHORT_RATIO

Retrieve historical long/short ratio snapshots for any cryptocurrency trading pair across exchanges, with customizable aggregation periods for trend analysis.

Instructions

Get global account long/short ratio history snapshot for a symbol

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

Input Schema

NameRequiredDescriptionDefault
symbolYesTrading pair, e.g., BTCUSDT or BTC
exchangeNoFutures exchange, e.g., Binance
periodNoAggregation period: 1h, 4h, 12h, 24h (maps to 1h/4h/12h/1d)24h
prettyFormatNoWhen true (default), returns a human-readable summary; when false, returns raw API-shaped data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states it returns a 'history snapshot' and does not mention data freshness, rate limits, aggregation behavior, or the effect of the prettyFormat parameter on output.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no wasted words.

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

Completeness3/5

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

Given no output schema, the description should explain what 'history snapshot' means and how 'prettyFormat' affects output. It is adequate but leaves gaps about return format and period default behavior.

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 coverage is 100%, so the baseline is 3. The description adds no additional parameter meaning beyond what the schema already provides.

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 clearly states the action ('Get'), the resource ('global account long/short ratio history snapshot'), and the target ('for a symbol'). It effectively distinguishes from sibling tools that handle funding rates, liquidations, open interest, etc.

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?

The description provides a clear context for when to use the tool (when needing long/short ratio data), but does not specify when not to use it or offer explicit alternatives among siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools