Skip to main content
Glama
horustechltd

horus-flow-mcp

by horustechltd

get_cross_exchange_flow

Detects market speculation vs real demand by analyzing Futures/Spot ratio and smart money divergence. Identifies hyper-speculation when ratio exceeds 8x, revealing potential vulnerability.

Instructions

Get Futures/Spot ratio, speculation index, and smart money divergence.

Reveals whether the market is driven by speculation (Futures) or real demand (Spot).
Futures/Spot > 8x = HYPER_SPECULATION (vulnerable to flush).
Also shows smart money divergence: are top traders positioned opposite to the crowd?

Args:
    symbol: Trading pair (default: BTCUSDT)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolNoBTCUSDT

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Main handler function that fetches cross-exchange flow data (Futures/Spot ratio, speculation index, smart money divergence) from the API endpoint /v1/intelligence/cross-exchange-flow and returns it as a JSON string.
    async def get_cross_exchange_flow(symbol: str = "BTCUSDT") -> str:
        """Get Futures/Spot ratio, speculation index, and smart money divergence.
        
        Reveals whether the market is driven by speculation (Futures) or real demand (Spot).
        Futures/Spot > 8x = HYPER_SPECULATION (vulnerable to flush).
        Also shows smart money divergence: are top traders positioned opposite to the crowd?
        
        Args:
            symbol: Trading pair (default: BTCUSDT)
        """
        data = await _fetch(f"/v1/intelligence/cross-exchange-flow?symbol={symbol}")
        return json.dumps(data, indent=2)
  • Docstring describes the input parameter (symbol, default BTCUSDT) and the output (Futures/Spot ratio, speculation index, smart money divergence).
    """Get Futures/Spot ratio, speculation index, and smart money divergence.
    
    Reveals whether the market is driven by speculation (Futures) or real demand (Spot).
    Futures/Spot > 8x = HYPER_SPECULATION (vulnerable to flush).
    Also shows smart money divergence: are top traders positioned opposite to the crowd?
    
    Args:
        symbol: Trading pair (default: BTCUSDT)
  • The @mcp.tool() decorator registers this function as an MCP tool named 'get_cross_exchange_flow'.
    @mcp.tool()
    async def get_cross_exchange_flow(symbol: str = "BTCUSDT") -> str:
  • The _fetch helper function is used by the handler to make HTTP requests to the RapidAPI endpoint.
    async def _fetch(endpoint: str) -> dict:
        """Fetch data from the live RapidAPI endpoint."""
        async with httpx.AsyncClient(timeout=10.0) as client:
            try:
                resp = await client.get(
                    f"{RAPIDAPI_BASE_URL}{endpoint}",
                    headers=HEADERS,
                )
                if resp.status_code == 200:
                    return resp.json()
                elif resp.status_code in [401, 403]:
                    return {
                        "error": True,
                        "signal": "UNAUTHORIZED",
                        "detail": "Invalid or missing RAPIDAPI_KEY. Please verify your RapidAPI subscription."
                    }
                elif resp.status_code == 429:
                    return {
                        "error": True,
                        "signal": "RATE_LIMITED",
                        "detail": "You have exceeded your RapidAPI quota. Please upgrade your plan."
                    }
                return {
                    "error": True,
                    "status_code": resp.status_code,
                    "detail": resp.text,
                }
            except Exception as e:
                return {
                    "error": True,
                    "detail": f"Network Error: {str(e)}"
                }
Behavior4/5

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

No annotations provided, so the description must fully convey behavior. It describes the returned indicators and gives a threshold, but does not mention rate limits, authentication, or potential side effects. As a read operation, it is adequately transparent.

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 concise, well-structured, and front-loaded with key information. It uses a clear header, explanation, and args section without any unnecessary words.

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?

Given the tool has a single optional parameter and an output schema, the description is complete. It explains the indicators, a threshold, and the parameter, making it fully self-contained for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, so the description must compensate. It explicitly states the symbol argument is a trading pair with a default of BTCUSDT, adding meaning beyond the schema's default value.

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 gets Futures/Spot ratio, speculation index, and smart money divergence. It explains what these indicators reveal, making the purpose unmistakable. The name matches the description, and it is distinct from sibling tools like get_crypto_flow.

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 explains what the tool reveals (speculation vs real demand) and provides a hyper-speculation threshold. It does not explicitly state when to use versus siblings or alternatives, but the context is clear for cross-exchange flow analysis.

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/horustechltd/horus-flow-mcp'

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