Skip to main content
Glama
bykarantelicom

bykaranteli-mcp

by bykarantelicom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Exchange coverage: OI, volume, funding and pegs across every exchange we snapshot

get_venue_markets
Read-only

Retrieves 10-minute venue market snapshots showing open interest, DEX versus CEX share, and funding dispersion across exchanges. Pass a symbol for per-venue rows or omit it to rank the largest markets.

Instructions

Call this when the user asks about total open interest across exchanges, which venues hold the most OI, DEX versus CEX share, funding dispersion between venues, or stablecoin pegs. Returns the latest 10-minute snapshot aggregates across every perpetual and spot feed we poll (the coverage field lists them); pass symbol for one coin's per-venue rows. Without symbol, rows holds the 30 venue markets with the largest open interest; pass symbol, or limit (up to 250) for more. Pass detail "compact" for a shorter page or "full" for the whole answer.

Input Schema

NameRequiredDescriptionDefault
limitNoOptional. Venue market rows without symbol, largest open interest first (default 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.
symbolNostring, optional base asset, e.g. BTC
history_daysNoReturn the hourly multi-venue open interest history (total, DEX share, OI-weighted funding) for this many days instead of the snapshot

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. Changed1 schema field changedv0.36.0
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Optional. Venue market rows without symbol, largest open interest first (default 30).",
+  "maximum": 250,
+  "minimum": 1,
+  "type": "integer"
+}
  3. Changed1 schema field changedv0.27.2
    • addedInput schema / properties / history_days
      Added value: +{
+  "description": "Return the hourly multi-venue open interest history (total, DEX share, OI-weighted funding) for this many days instead of the snapshot",
+  "maximum": 90,
+  "minimum": 1,
+  "type": "integer"
+}
  4. Addedv0.9.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful operational detail beyond annotations: the data is the latest 10-minute snapshot, coverage is listed in a coverage field, default rows are the 30 largest-OI venue markets, limit caps at 250, compact/full changes truncation behavior, and full responses stay under a 100,000 character ceiling. It omits the history_days mode in the description, though the schema covers it.

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 front-loaded with the when-to-call use cases, then moves directly into return behavior and page-size controls. Every sentence carries operational information, and there is no redundant restatement of the title or schema.

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

Completeness4/5

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

There is no output schema, so the description carries the burden of explaining returns. It does this well for the snapshot mode by describing coverage, rows, default 30-row behavior, compact/full trimming, and the character ceiling. It is slightly incomplete because it does not describe the history_days return mode, though the schema parameter description does.

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. The description still adds value by explaining that without symbol the rows are the 30 largest-OI venue markets, that symbol switches to one coin's per-venue rows, that limit can raise the row count up to 250, and how detail 'compact' versus 'full' changes the page. It does not mention history_days at all, leaving that important mode to the schema.

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 description names concrete user questions (cross-exchange OI, top OI venues, DEX/CEX share, funding dispersion, stablecoin pegs) and states that it returns 10-minute snapshot aggregates across all polled perpetual and spot feeds. It is clearly scoped, but it does not explicitly distinguish itself from nearby siblings such as get_venue_share or get_open_interest, so a 4 rather than a 5.

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 gives strong trigger conditions: use when the user asks about total OI across exchanges, which venues hold the most OI, DEX versus CEX share, funding dispersion, or stablecoin pegs. It also explains the symbol/no-symbol branching and limit/detail behavior. It stops short of naming alternative tools or when not to use this one.

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