Skip to main content
Glama
bykarantelicom

bykaranteli-mcp

by bykarantelicom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Options tape: biggest prints and premium flow (BTC + ETH)

get_options_flow
Read-only

Track 24h crypto options flow: compare call versus put premium bought, measure block-trade share, count multi-leg structures, and list the largest prints from the last 48 hours by strike, IV, and venue.

Instructions

Call this when the user asks what big options players are buying, about block trades, or whether call or put premium dominates today. Returns 24h call vs put premium bought (net of the sold legs of the same multi-leg block or combo, so a spread counts its net premium), the block-trade share, the multi-leg structure count, and the largest prints of the last 48 hours with strikes, premium, IV, structure id and venue (Deribit or OKX). Updated every 15 minutes. 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. 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. First observedv0.5.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly and open-world, so the safety profile is covered; the description still adds genuine behavioral context beyond them. The net-of-sold-legs explanation ('a spread counts its net premium') is a real methodological disclosure that prevents misreading the call/put premium split, and the 15-minute refresh cadence plus the Deribit/OKX venue scope tell the agent how fresh and how broad the data is.

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 usage trigger, then the return payload, then freshness, then the parameter — a sensible order. It is dense but nearly every clause carries information (venue, 48h window, net premium, cadence); only the trailing detail-parameter sentence is redundant with the 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?

With no output schema, the description carries the return-value burden and does it well: it enumerates the four returned quantities and the fields on each print, plus refresh cadence and data sources. The one gap is asset coverage — BTC/ETH scope appears only in the title, not the body, and there is no symbol parameter to narrow it, so an agent could over-generalize the universe.

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's own description already spells out compact vs full, the trimmed list, and the 100,000-character ceiling. The description's sentence 'Pass detail "compact" for a shorter page or "full" for the whole answer' restates the schema with no added syntax, default, or interaction detail, so baseline 3 applies.

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?

States a concrete verb-plus-resource with unusual specificity: it returns 24h call vs put premium, block-trade share, multi-leg structure count, and the largest prints of the last 48h with strikes, IV, structure id and venue. That scope is clearly distinct from a point-in-time options snapshot or chain listing. It never names a sibling tool, so an agent must infer the boundary with get_options_snapshot, get_options_chain and get_iv_surface.

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 invocation trigger — 'Call this when the user asks what big options players are buying, about block trades, or whether call or put premium dominates today' — giving three concrete question patterns. There are no exclusions or named alternatives, so an agent asking 'what is the option chain' or 'what's IV now' gets no routing guidance.

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