Skip to main content
Glama
SwapHunt crypto market context

SwapHunt crypto market context

Official

get_green_candle_streak

Measure how many green candles a coin has in a row on 1h, 4h, or 1d intervals and check the historical odds that the next candle is green.

Instructions

Use when the user asks how many green candles in a row a coin has. Returns the streak on 1h, 4h or 1d and how often the next candle was green after such streaks. Top 50 Hyperliquid perpetuals by 30-day volume only (see get_supported_assets), others unpaid. Ex: symbol=BTC, interval=1d Costs $0.003 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_green_candle_streak"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolNoBTC
intervalNo4h

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does real work: it discloses the data universe restriction (top 50 Hyperliquid perpetuals by 30-day volume), that the response includes a base-rate statistic, and a per-call cost of $0.003 USDC. It does not explain how that base rate is computed (sample size/window) or what happens when a symbol falls outside the top 50 beyond the vague phrase 'others unpaid'.

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 tight sentences: trigger first, then return contents, then universe limitation, then cost. Every sentence carries information an agent needs, with no filler or repetition of the name.

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?

There is no output schema, so the description must describe the return — and it does, naming both the streak and the follow-through frequency, plus the cost and universe limits. The remaining gaps are the ambiguity of 'others unpaid' and the unstated computation basis for the historical frequency.

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?

Schema coverage is 0% with no enums and no parameter descriptions, so the description must compensate — and it largely does by enumerating the accepted intervals (1h, 4h, 1d) and giving a concrete example (symbol=BTC, interval=1d). It does not state that both parameters are optional or what the defaults (BTC, 4h from the schema) mean behaviorally.

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?

States a specific verb+resource ('how many green candles in a row a coin has') and then quantifies the return: the current streak on 1h/4h/1d plus the historical frequency of a green follow-up candle. That is distinguishable from every sibling in the list, none of which report candle streaks.

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?

Opens with an explicit trigger ('Use when the user asks how many green candles in a row a coin has') and points to get_supported_assets for the covered universe. It gives no when-not condition or named alternative for adjacent questions such as overbought/breakout checks, so it stops short of full routing guidance.

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