Skip to main content
Glama
bykarantelicom

bykaranteli-mcp

by bykarantelicom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Positioning: long/short ratios, taker buy/sell and CVD across exchanges

get_positioning
Read-only

Retrieve long/short, taker buy/sell and cumulative volume delta statistics for Binance perpetuals across venues to gauge whether retail or top traders are net long or short.

Instructions

Call this when the user asks about the long/short ratio, whether retail or top traders are net long or short, the taker buy/sell ratio, or CVD (cumulative volume delta) for a perpetual. Returns exchange-published statistics for the 30 most traded Binance USDT perps on every perpetual venue the positioning board records (Binance global and top-trader ratios, Bybit share long, OKX ratios and taker volume, Gate account and top-trader ratios, HTX elite ratios, Bitget account and position ratios) and CVD series for BTC, ETH and SOL; refreshed every 15 minutes. Without symbol, the 10 most traded perps and the newest 24 points of each CVD series; pass symbol, limit or cvd_points for more. Pass detail "compact" for a shorter page or "full" for the whole answer.

Input Schema

NameRequiredDescriptionDefault
limitNoOptional. Perps without symbol, most traded first (default 10, up to 30).
detailNoOptional. "compact": a shorter page than the default (fewer rows, newest points kept, rounded figures, long text cut, grids left out; every cut named in trimmed). "full" or true: the whole route answer, still under the 100,000 character ceiling (the largest boards answer the ceiling note then: narrow them with symbol, limit or days instead). Omitted or false: the default first page.
symbolNoOne Binance symbol, e.g. BTCUSDT
cvd_pointsNoOptional. Newest points per CVD series (1h and 5m); default 24 without symbol, every point with one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / detail
      Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "enum": [
+        "compact",
+        "full"
+      ],
+      "type": "string"
+    }
+  ],
+  "description": "Optional. \"compact\": a shorter page than the default (fewer rows, newest points kept, rounded figures, long text cut, grids left out; every cut named in trimmed). \"full\" or true: the whole route answer, still under the 100,000 character ceiling (the largest boards answer the ceiling note then: narrow them with symbol, limit or days instead). Omitted or false: the default first page."
+}
  2. Changed2 schema fields changedv0.36.0
    • addedInput schema / properties / cvd_points
      Added value: +{
+  "description": "Optional. Newest points per CVD series (1h and 5m); default 24 without symbol, every point with one.",
+  "maximum": 288,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Optional. Perps without symbol, most traded first (default 10, up to 30).",
+  "maximum": 30,
+  "minimum": 1,
+  "type": "integer"
+}
  3. Addedv0.27.2

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds real behavioral context the annotations don't: a 15-minute refresh cadence, the exact venue coverage list, and the default page shape when no symbol is given. It stops short of describing error behavior or what happens when a venue is unreachable, so not a 5.

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?

Front-loaded with the trigger condition, then returns, then defaults, then parameters — a sensible information order with essentially no filler. It is a single dense paragraph, though, and the venue enumeration is long enough that slightly tighter structure (or bulleting) would scan better.

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?

No output schema exists, so the description carries the return-value burden and does: venue-by-venue contents, CVD coverage limited to BTC/ETH/SOL, the 100,000-character ceiling note on 'full', and the trimmed-field reporting on 'compact'. An agent has everything needed to call this correctly.

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 100%, so the baseline is 3, but the description earns an extra point by stating the coupled defaults — no symbol yields the 10 most traded perps plus 24 newest CVD points, and passing symbol/limit/cvd_points widens that. The detail enum is explained in the description as well as the schema.

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?

Names the exact analytics returned (long/short ratio, taker buy/sell ratio, CVD) and the exact population (Binance USDT perps across every recorded venue), with venue-level enumeration. This is clearly separable from siblings like get_cot_positioning or get_pressure_scores without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Opens with an explicit invocation trigger: 'Call this when the user asks about the long/short ratio... net long or short... taker buy/sell ratio, or CVD for a perpetual.' It further routes between the default view and the symbol/limit/detail variants, so the agent knows both when to call it and how to shape the call.

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