Skip to main content
Glama
bykarantelicom

bykaranteli-mcp

by bykarantelicom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Venue lead-lag: who moves first (Coinbase, Kraken, Binance)

get_lead_lag
Read-only

Identify which exchange leads price discovery and whether spot or perpetual futures moves first using per-pair daily cross-correlations at lags -3 to +3 and lead asymmetry shares.

Instructions

Call this when the user asks which exchange leads price discovery or whether spot or perp moves first. Returns per-pair daily cross-correlations of one-minute returns at lags -3..+3 and the lead asymmetry, with the share of days each venue led. Each pair's daily rows cover the last 7 days (its summary covers the whole window); pass days (up to 30) for more.

Input Schema

NameRequiredDescriptionDefault
daysNoOptional. Daily rows per pair, newest kept (default 7, up to 30).

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 / days
      Added value: +{
+  "description": "Optional. Daily rows per pair, newest kept (default 7, up to 30).",
+  "maximum": 30,
+  "minimum": 1,
+  "type": "integer"
+}
  3. Addedv0.9.0

TDQS

A4.5/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 description's job is supplementary and it delivers: it discloses the return shape (daily rows vs. whole-window summary), the lag range, and the rolling coverage window. It does not mention rate limits or data-source freshness, keeping it just short of 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.

Conciseness5/5

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

Three sentences, front-loaded with the trigger before the return description, then the parameter nuance. Nothing is redundant or padding.

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?

With no output schema, the description must explain return values, and it does — lag structure, lead asymmetry, and per-venue share of leading days. Combined with the single optional well-documented parameter and read-only annotations, an agent has everything needed to call it 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 baseline is 3; the description goes slightly further by explaining the consequence of the parameter — the default 7-day daily rows versus the whole-window summary, and that 'days' up to 30 extends coverage. It largely restates the schema's default/max, so the added value is modest.

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 a specific analytical artifact (per-pair daily cross-correlations of one-minute returns at lags -3..+3 plus lead asymmetry) rather than restating the tool name. The venue-focus (Coinbase, Kraken, Binance) and spot-vs-perp framing let an agent tell it apart from generic correlation siblings like get_correlations.

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?

Opens with an explicit trigger: 'Call this when the user asks which exchange leads price discovery or whether spot or perp moves first.' That is a clear usage condition, but no exclusion or named alternative (e.g. get_correlations) is offered for overlapping questions.

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