Skip to main content
Glama
bykarantelicom

bykaranteli-mcp

by bykarantelicom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Coverage registry: which venues and data types we collect, how, and how fresh

get_coverage
Read-only

Check which exchanges and live data feeds are covered, whether feeds are complete or sampled, when venue collection began, and how fresh records are before relying on crypto derivatives data.

Instructions

Call this when the user asks which exchanges sit behind a ByKaranteli number, whether a feed is complete or sampled, since when a venue is collected, or how fresh the data is. Returns the live coverage registry: liquidation feeds per venue with kind and last record, snapshot feeds per venue and market, funding arbitrage legs, positioning sources, whale tape, spot minutes and the Hyperliquid whale scan with freshness. snapshots[].country is the jurisdiction only when the venue states one; it is null for most venues, so do not read null as unknown risk. By default the first 30 snapshot feeds, English notes only and no per-venue matrix cells; pass detail "full" for the full registry. Pass detail "compact" for a shorter page or "full" for the whole answer.

Input Schema

NameRequiredDescriptionDefault
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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 / anyOf
      Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "enum": [
+      "compact",
+      "full"
+    ],
+    "type": "string"
+  }
+]
    • changedInput schema / properties / detail / description
      Previous value: -"Optional. true: every snapshot feed, the zh, ru and ko notes and the venue by product matrix cells (default false)."New value: +"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."
    • removedInput schema / properties / detail / type
      Removed value: -"boolean"
  2. Changed1 schema field changedv0.36.0
    • addedInput schema / properties / detail
      Added value: +{
+  "description": "Optional. true: every snapshot feed, the zh, ru and ko notes and the venue by product matrix cells (default false).",
+  "type": "boolean"
+}
  3. Addedv0.27.2

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the read-only annotation, the description discloses important behavioral traits: the default response includes only the first 30 snapshot feeds, English notes only, and no per-venue matrix cells; detail modes alter truncation; and null country values should not be interpreted as unknown risk. These are substantive operational details an agent could not infer from annotations alone.

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?

The description is front-loaded with the triggering question types and then moves to return contents, caveats, and detail modes. It is dense but mostly efficient; the detail-mode explanation repeats information already present in the schema, which is a minor redundancy.

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?

There is no output schema, so the description carries the burden of explaining return contents, which it does thoroughly by listing the registry sections and freshness information. It also covers default truncation, the meaning of null country values, and how detail modes change the response, leaving no major gaps for a one-parameter read-only registry tool.

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% and the parameter description already explains compact, full, true, and default behavior in detail. The tool description restates the default and detail modes but does not add 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 states a specific resource — the live coverage registry — and enumerates exactly what it contains: liquidation feeds, snapshot feeds, funding arbitrage legs, positioning sources, whale tape, spot minutes, and Hyperliquid scan freshness. It clearly distinguishes itself from metric-oriented siblings by serving as the registry explaining what data is collected and how fresh it is.

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 an explicit triggering condition: 'Call this when the user asks which exchanges sit behind a ByKaranteli number, whether a feed is complete or sampled, since when a venue is collected, or how fresh the data is.' This is clear usage context, but it does not name any sibling alternative or state when not to use 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