Skip to main content
Glama
VENTURE-AI-LABS

CryptoDataAPI MCP Server

by VENTURE-AI-LABS
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

get_etf_flows

Retrieve daily net inflow/outflow data for BTC, ETH, SOL, or XRP spot ETFs to monitor institutional demand and selling pressure across major ETF issuers.

Instructions

Get ETF flow data for BTC, ETH, SOL, or XRP spot ETFs. Shows daily net inflows/outflows across all major ETF issuers (BlackRock, Fidelity, Grayscale, etc.). Consistent positive flows signal institutional demand; negative flows signal institutional selling. BTC ETF flows have been a major market driver since January 2024.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assetYesAsset for ETF flows: btc, eth, sol, or xrp

Implementation Reference

  • src/tools/etf-flows.ts:18-20 (handler)
    The handler function that executes the request to retrieve ETF flow data for the specified asset.
    export async function handler(args: z.infer<typeof schema>) {
  return apiGet(`/api/v1/market-intelligence/etf/${args.asset}/flows`);
}
  • src/tools/etf-flows.ts:12-16 (schema)
    Input validation schema for the get_etf_flows tool, defining the required asset type.
    export const schema = z.object({
  asset: z
    .enum(["btc", "eth", "sol", "xrp"])
    .describe("Asset for ETF flows: btc, eth, sol, or xrp"),
});
  • src/index.ts:27-45 (registration)
    Registration of the etfFlows tool into the main server tool list in src/index.ts.
    import * as etfFlows from "./tools/etf-flows.js";
import * as options from "./tools/options.js";

// Prompts
import * as marketBriefing from "./prompts/market-briefing.js";

const tools = [
  daily,
  marketHealth,
  fearGreed,
  fundingRates,
  liquidations,
  openInterest,
  btcCycle,
  coinProfile,
  searchCoins,
  macro,
  stablecoinFlows,
  etfFlows,

Tool Definition Quality

A3.9/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds context about the data's significance ('Consistent positive flows signal institutional demand; negative flows signal institutional selling') and historical relevance ('BTC ETF flows have been a major market driver since January 2024'), but does not detail operational aspects like data freshness, rate limits, or error handling.

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 appropriately sized and front-loaded, starting with the core functionality. The first sentence covers the purpose, and subsequent sentences add valuable context without redundancy. However, the historical note about BTC flows, while informative, could be considered slightly extraneous for pure tool selection.

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?

Given the tool's low complexity (1 parameter, no output schema, no annotations), the description is largely complete. It explains what the tool does, why it's useful, and provides context. The main gap is the lack of output details, but with no output schema, this is a minor omission for a simple data retrieval 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%, with the parameter 'asset' fully documented in the schema (enum values and description). The description adds no additional parameter semantics beyond what the schema provides, such as explaining the implications of choosing different assets, so it meets the baseline score of 3.

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 clearly states the tool's purpose with specific verbs ('Get ETF flow data') and resources ('BTC, ETH, SOL, or XRP spot ETFs'), distinguishing it from siblings by focusing on ETF flows rather than other crypto metrics like fear/greed indices or funding rates. It explicitly mentions what data is shown ('daily net inflows/outflows across all major ETF issuers').

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 provides clear context for when to use the tool—to analyze institutional demand or selling signals for specific assets via ETF flows—and implies usage by mentioning market drivers. However, it does not explicitly state when not to use it or name alternatives among sibling tools, such as 'get_stablecoin_flows' for different flow types.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/VENTURE-AI-LABS/cryptodataapi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server