Skip to main content
Glama
kukapay

crypto-liquidations-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_liquidationsA

Retrieve the latest liquidation events from Binance in a table format.

Args:
    limit (int): The maximum number of liquidation events to return (default: 10, max: 1000).
    ctx (Context, optional): The MCP context for logging and server interaction. Defaults to None.

Returns:
    str: A Markdown table containing the latest liquidation events, sorted by timestamp in descending order.

Prompts

Interactive templates invoked by user choice

NameDescription
analyze_liquidationsGenerate a prompt to analyze liquidation trends across all symbols

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 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as retrieving liquidation events from Binance, making it distinct by default.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name 'get_latest_liquidations' follows a clear verb_noun pattern, which would be consistent if more tools were added.

Tool Count2/5

A single tool is too few for a server focused on crypto liquidations, as it severely limits functionality. The scope suggests a need for more operations, such as filtering by asset, time range, or exchange, making this feel incomplete and thin.

Completeness2/5

The tool surface is significantly incomplete for the domain of crypto liquidations. While it provides a basic retrieval function, there are obvious gaps, such as no ability to filter by parameters like asset type, exchange, or time period, which are essential for practical use.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources