Skip to main content
Glama
kukapay

etf-flow-mcp

by kukapay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get_etf_flowA
Fetch historical ETF flow data for BTC or ETH from CoinGlass API and return as a Markdown table.

Parameters:
    coin (str): Cryptocurrency to query ('BTC' or 'ETH').

Returns:
    str: Markdown table with ETF flow data (tickers as columns, dates as rows, with total column).

Prompts

Interactive templates invoked by user choice

NameDescription
etf_flow_prompt Create a prompt for querying BTC or ETH ETF flow data. Args: coin (str): Cryptocurrency to query ('BTC' or 'ETH'). Returns: List[PromptMessage]: List of prompt messages to guide LLM interaction.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.9/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is singular and clearly defined.

Naming Consistency5/5

The single tool name 'get_etf_flow' follows a clear verb_noun pattern. Since there are no other tools, consistency is inherently perfect.

Tool Count2/5

One tool is too few for the server's apparent scope of ETF flow data analysis. It lacks complementary tools like historical trends, comparisons, or metadata, making the surface feel thin and incomplete for the domain.

Completeness2/5

The tool set is severely incomplete for ETF flow analysis. It only fetches data for BTC or ETH, missing operations like multi-coin queries, date range filtering, summary statistics, or visualization, which are essential for comprehensive coverage.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources