Skip to main content
Glama
bykarantelicom

bykaranteli-mcp

by bykarantelicom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

US spot Bitcoin and Ethereum ETF daily flows

get_etf_flows
Read-only

Retrieve daily net inflows, cumulative flows, and total net assets for Bitcoin, Ethereum, and Solana US spot ETFs. Get per-trading-day data for the past 14 months.

Instructions

Call this when the user asks about Bitcoin, Ethereum or Solana spot ETF flows: daily net inflows or outflows, cumulative flow since launch, or total net assets of the US spot ETFs (IBIT, FBTC, ETHA and the rest). Returns one row per finalized US trading day and asset with net inflow, total net assets, cumulative inflow and value traded, all in USD. About 14 months of history.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoHow many most recent trading days to return (default 10).
assetNoFilter to one asset (BTC, ETH or SOL, SOL since 2026-09-02). Omit for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.27.2
    • changedInput schema / properties / asset / description
      Previous value: -"Filter to one asset. Omit for both."New value: +"Filter to one asset (BTC, ETH or SOL, SOL since 2026-09-02). Omit for all."
    • changedInput schema / properties / asset / enum
      Previous value: -[
-  "BTC",
-  "ETH"
-]New value: +[
+  "BTC",
+  "ETH",
+  "SOL"
+]
  2. First observedv0.5.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses important behavior: returns one row per finalized US trading day and asset, lists the exact fields (net inflow, total net assets, cumulative inflow, value traded), states values are in USD, and notes roughly 14 months of history. This gives an agent a clear model of what the call will produce without contradicting the annotations.

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 three sentences with no filler: a front-loaded trigger phrase, a concrete list of returned fields, and a useful history-length detail. Every sentence earns its place and the structure lets an agent quickly decide whether to invoke the tool.

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?

Even though there is no output schema, the description fully explains the return shape: one row per finalized trading day and asset, with all five key fields and currency. Combined with complete parameter documentation in the schema, nothing essential is missing for an agent to understand what the tool returns and how to call it.

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%, so the schema already documents both parameters fully, including the enum and the days range. The description adds slight context around the output rows being per trading day and per asset, which indirectly clarifies the parameters, but it does not materially elevate meaning beyond the schema.

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 names a specific resource — US spot Bitcoin, Ethereum, and Solana ETF flows — and a concrete verb ('Call this when the user asks about...'). It covers the tool's key data types (daily inflows/outflows, cumulative flow, net assets) and its scope, making it instantly distinguishable from the sibling tools, none of which target ETF flows.

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?

The description explicitly states when to call the tool: when the user asks about BTC, ETH, or SOL spot ETF flows, including specific metrics like daily net flows, cumulative flow, and net assets. It gives clear invocation context but does not discuss when not to use it or name alternative tools, so it stops just short of full when/when-not 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