Skip to main content
Glama
horustechltd

horus-flow-mcp

by horustechltd

get_market_climate

Determine current market mode (CHOP, TREND, RANGE) and health (HEALTHY, FRAGILE) to inform trading strategy and position sizing adjustments.

Instructions

Get current market mode and health status.

Returns market mode (CHOP, TREND, RANGE) and health (HEALTHY, FRAGILE).
CHOP = only scalps work, TREND = directional trades, RANGE = mean-reversion.
If health is FRAGILE, reduce all position sizes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'get_market_climate' tool. It fetches market climate data (CHOP/TREND/RANGE mode and HEALTHY/FRAGILE health status) from the /v1/intelligence/climate endpoint and returns it as JSON.
    async def get_market_climate() -> str:
        """Get current market mode and health status.
        
        Returns market mode (CHOP, TREND, RANGE) and health (HEALTHY, FRAGILE).
        CHOP = only scalps work, TREND = directional trades, RANGE = mean-reversion.
        If health is FRAGILE, reduce all position sizes.
        """
        data = await _fetch("/v1/intelligence/climate")
        return json.dumps(data, indent=2)
  • Registration of get_market_climate as an MCP tool via the @mcp.tool() decorator on line 240.
    @mcp.tool()
  • The _fetch helper used by get_market_climate to make the HTTP request to the RapidAPI endpoint and handle errors (auth, rate limiting, network).
    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)}"
                }
Behavior5/5

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

No annotations provided, so description fully discloses return values and implications. Explains what each market mode means for trading strategy and advises position sizing adjustment for FRAGILE health.

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?

Four concise sentences front-loaded with purpose. Every sentence adds value. No redundancy.

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?

Fully explains the tool's output and its interpretation. With no parameters and an output schema, the description is complete and self-contained.

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?

No parameters exist, so baseline 4. Description adds value by explaining the meaning of the returned data beyond the schema.

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?

Clearly states it returns market mode (CHOP, TREND, RANGE) and health (HEALTHY, FRAGILE). Distinguishes from siblings like get_market_intelligence by focusing on climate status.

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?

Explicitly describes when to use (get current mode/health) and gives actionable advice for FRAGILE health. Doesn't explicitly mention when not to use or alternatives, but context is sufficient.

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