Skip to main content
Glama
bykarantelicom

bykaranteli-mcp

by bykarantelicom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Leverage tiers: max leverage and maintenance margin per perpetual on every venue

get_leverage_tiers
Read-only

Returns current leverage ladders per exchange, including tier caps, max leverage, and maintenance margin rates, plus a change log so you can compare venues or see recent leverage cuts.

Instructions

Call this when the user asks how much leverage an exchange allows on a coin, what the maintenance margin or risk limit ladder is, which venue offers the highest leverage for a symbol, or whether an exchange recently cut leverage. Returns the current ladder per venue (tier, notional floor and cap, max leverage, maintenance margin rate) recorded daily by ByKaranteli, plus a change log. Pass symbol for one base asset (e.g. SOL) and venue for one exchange (bybit, okx, gate, htx, bitget, mexc). Without symbol, the first 30 rows of each list and the first 5 tiers of each ladder; pass symbol for every tier, or limit (up to 300).

Input Schema

NameRequiredDescriptionDefault
limitNoOptional. Rows per list without symbol (default 30).
venueNostring, optional venue id, e.g. bybit
symbolNostring, optional base asset, e.g. BTC

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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"
  2. Changed1 schema field changedv0.36.0
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Optional. Rows per list without symbol (default 30).",
+  "maximum": 300,
+  "minimum": 1,
+  "type": "integer"
+}
  3. Addedv0.27.2

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds real context beyond that — provenance (recorded daily by ByKaranteli), a change log alongside current tiers, and truncation behavior (first 30 rows / first 5 tiers, up to 300) so the agent can anticipate incomplete results.

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?

Triggers come first, then return contents, then parameter behavior — well front-loaded. The final sentence packs three conditional clipping rules together and reads slightly run-on, costing a bit of clarity.

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, yet the description enumerates the returned fields and the change log, and discloses pagination/clipping defaults. An agent has everything needed to call it and interpret the response without guessing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% so baseline is 3, but the description adds materially: it gives the base-asset convention for symbol (e.g. SOL), enumerates valid venue ids that the schema lacks (bybit, okx, gate, htx, bitget, mexc), and explains the symbol/limit interaction that the schema leaves implicit.

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 resource (leverage ladder per venue: tier, notional floor/cap, max leverage, maintenance margin) and the exact questions it answers, which cleanly separates it from siblings like get_fee_table or get_venue_profile.

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 explicit triggers (leverage allowance per coin, maintenance margin/risk limit ladder, highest-leverage venue, recent leverage cuts), so an agent knows precisely when to select it. It also explains the consequence of omitting symbol versus supplying it.

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