Skip to main content
Glama
kukapay

dex-metrics-mcp

by kukapay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

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_latest_trading_volume_by_dexA
Retrieve the latest 24-hour and 7-day trading volume by decentralized exchange (DEX).

Args:
    limit (int, optional): Maximum number of rows to retrieve from the query. Defaults to 1000.

Returns:
    str: A markdown-formatted table of trading volume data, or an error message if the query fails.
get_latest_trading_volume_by_aggregatorB
Retrieve the latest 24-hour and 7-day trading volume by aggregator.

Args:
    limit (int, optional): Maximum number of rows to retrieve from the query. Defaults to 1000.

Returns:
    str: A markdown-formatted table of trading volume data, or an error message if the query fails.
get_weekly_trading_volume_by_chainB
Retrieve weekly trading volume by blockchain.

Args:
    limit (int, optional): Maximum number of rows to retrieve from the query. Defaults to 1000.

Returns:
    str: A markdown-formatted pivot table of trading volume data, or an error message if the query fails.
get_daily_trading_volume_by_dexA
Retrieve daily trading volume by decentralized exchange (DEX).

This tool fetches daily trading volume data for various DEXs from a Dune Analytics query and returns it in a markdown-formatted pivot table, with dates as the index and DEX projects as columns.

Args:
    limit (int, optional): Maximum number of rows to retrieve from the query. Defaults to 1000.

Returns:
    str: A markdown-formatted pivot table of trading volume data, or an error message if the query fails.
get_weekly_trading_volume_by_dexA
Retrieve weekly trading volume by decentralized exchange (DEX).

This tool fetches weekly trading volume data for various DEXs from a Dune Analytics query and returns it in a markdown-formatted pivot table, with dates as the index and DEX projects as columns.

Args:
    limit (int, optional): Maximum number of rows to retrieve from the query. Defaults to 1000.

Returns:
    str: A markdown-formatted pivot table of trading volume data, or an error message if the query fails.
get_monthly_trading_volume_by_dexA
Retrieve monthly trading volume by decentralized exchange (DEX).

This tool fetches monthly trading volume data for various DEXs from a Dune Analytics query and returns it in a markdown-formatted pivot table, with dates as the index and DEX projects as columns.

Args:
    limit (int, optional): Maximum number of rows to retrieve from the query. Defaults to 1000.

Returns:
    str: A markdown-formatted pivot table of trading volume data, or an error message if the query fails.
get_yoy_monthly_trading_volume_by_aggragatorA
Retrieve year-over-year monthly trading volume by aggregator.

This tool fetches year-over-year monthly trading volume data for aggregators from a Dune Analytics query and returns it in a markdown-formatted pivot table, with years as the index and months as columns.

Args:
    limit (int, optional): Maximum number of rows to retrieve from the query. Defaults to 1000.

Returns:
    str: A markdown-formatted pivot table of trading volume data, or an error message if the query fails.
get_weekly_solana_trading_volume_by_dexA
Retrieve weekly trading volume by decentralized exchange (DEX) on the Solana blockchain.

This tool fetches weekly trading volume data for DEXs on Solana from a Dune Analytics query and returns it in a markdown-formatted pivot table, with dates as the index and DEX projects as columns.

Args:
    limit (int, optional): Maximum number of rows to retrieve from the query. Defaults to 1000.

Returns:
    str: A markdown-formatted pivot table of trading volume data, or an error message if the query fails.
get_weekly_trading_volume_by_frontendA
Retrieve 7-day trading volume by frontend.

This tool fetches 7-day trading volume data for different frontends from a Dune Analytics query and returns it in a markdown-formatted table, sorted by volume in descending order.

Args:
    limit (int, optional): Maximum number of rows to retrieve from the query. Defaults to 1000.

Returns:
    str: A markdown-formatted table of trading volume data, or an error message if the query fails.
get_daily_trading_volume_by_telegram_botA
Retrieve daily trading volume by Telegram bot.

This tool fetches daily trading volume data for Telegram bots from a Dune Analytics query and returns it in a markdown-formatted pivot table, with dates as the index and bot names as columns.

Args:
    limit (int, optional): Maximum number of rows to retrieve from the query. Defaults to 1000.

Returns:
    str: A markdown-formatted pivot table of trading volume data, or an error message if the query fails.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.7/5.0

Scored across 10 tools

Disambiguation3/5

The tools have overlapping purposes with multiple variations of trading volume retrieval by different dimensions (DEX, chain, frontend, etc.), which could cause confusion. However, the descriptions clearly specify the breakdown dimension and timeframe, helping to distinguish them. There is some ambiguity between similar tools like get_weekly_trading_volume_by_dex and get_weekly_solana_trading_volume_by_dex, but the descriptions clarify the scope.

Naming Consistency5/5

All tools follow a consistent snake_case naming pattern with a clear get_<timeframe>_trading_volume_by_<dimension> structure. The naming is predictable and uniform across all 10 tools, making it easy to understand what each tool does based on its name alone.

Tool Count4/5

With 10 tools, the count is reasonable for a metrics server focused on trading volume data. However, there is some redundancy with multiple tools covering similar dimensions (e.g., multiple DEX-focused tools with different timeframes), which makes the set feel slightly heavy but still within appropriate bounds for the domain.

Completeness3/5

The server covers various dimensions (DEX, chain, frontend, aggregator, Telegram bot) and timeframes (daily, weekly, monthly, latest, YoY), but there are notable gaps. For example, there is no tool for creating, updating, or deleting data, and coverage is inconsistent across dimensions (e.g., no monthly data for chains or frontends). The surface is focused on retrieval only, which limits completeness for a full metrics management system.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources