Skip to main content
Glama
SwapHunt crypto market context

SwapHunt crypto market context

Official

get_market_regime

Determine whether BTC is bullish, bearish, or neutral by comparing Hyperliquid perpetual price to its 20-period EMA on 12-hour candles; returns EMA, distance, and slope.

Instructions

Use when the user asks whether the crypto market (BTC) is bullish, bearish or neutral. Returns the regime from the BTC price on Hyperliquid perpetuals vs its 20-period EMA on 12h candles, with EMA, distance and slope; updates 00:00 and 12:00 UTC. BTC only. Ex: no parameters Costs $0.010 USDC per call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_market_regime"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the computation (BTC perpetual price vs 20-period EMA on 12h candles), the refresh schedule (00:00 and 12:00 UTC), the asset restriction, and the cost ($0.010 USDC per call). It stops short of stating latency, failure behavior, or how 'slope' and 'distance' are measured, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the trigger, followed by method, cadence, scope, and cost — each sentence adds new information. The telegraphic fragments ('BTC only. Ex: no parameters') are slightly clipped but cost little.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-argument, annotation-free tool with no output schema, the description supplies what an agent needs: the signal definition, the possible regime values, the returned components (EMA, distance, slope), and the update cadence. Only the precise response field names and error behavior remain unstated.

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 tool takes zero parameters, so the baseline is 4. The description confirms this explicitly with 'Ex: no parameters', leaving no ambiguity about whether arguments are expected.

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?

Names a specific verb and resource ('Returns the regime from the BTC price ... vs its 20-period EMA on 12h candles') and scopes it tightly with 'BTC only'. An agent can distinguish this regime classifier from siblings like get_chop_detection or get_alt_season without opening any schema.

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 opening sentence gives an explicit trigger condition: 'Use when the user asks whether the crypto market (BTC) is bullish, bearish or neutral.' It does not name alternatives or state when NOT to use it, but the trigger is clear enough to route the call.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.