Skip to main content
Glama

Create an OwlChart alert

create_alert

Sets an alert on OwlChart data, checked every minute. Types: price_above = price goes above the threshold (dollars); price_below = price goes below the threshold (dollars); oi_change = open interest summed across 13 exchanges moves by the threshold percent from when the alert was set (negative number for a drop); magnet_hit = price reaches the liquidity magnet above or below that existed when the alert was set (no threshold needed); funding_extreme = average funding across exchanges reaches the threshold percent per funding period, either sign (for example 0.05); etf_flip = OwlChart spot ETF verdict for BTC or ETH changes (BUYING, SELLING, MIXED); coin must be BTC or ETH; stablecoin_mint = net stablecoins minted minus burned over 24 hours (all tracked issuers, read from the contracts) crosses the threshold in millions of dollars (negative number for net burn); coin is ignored; large_transfer = a single on-chain transfer of the token (coin = token hub id, e.g. USD1, USDC, BUIDL) of at least the threshold in millions of dollars is seen in the last hour (Ethereum contracts; see get_token_hub); reg_keyword = a new regulatory event whose title contains the keyword given in note appears on the Regulatory Radar (coin is ignored; threshold not needed); stable_print = v5.853: a big print of USDT or USDC (coin = USDT or USDC) lands on an exchange: $50M in one transfer or $100M inside an hour from the issuer treasury (no threshold needed); stable_pulse = v5.853: the Stablecoin Pulse label of USDT or USDC (coin) changes, BULLISH, NEUTRAL or BEARISH (no threshold needed); wlfi_buyback_surge = v5.888: the estimated WLFI buyback flow of the last 24 hours (World Liberty buying on Aster) reaches the threshold times its 7 day pace (for example 2 for double); coin must be WLFI; wlfi_buyback_stop = v5.888: the estimated WLFI buyback flow of the last 24 hours falls under $20,000, the buying has paused or ended (no threshold needed); coin must be WLFI; gold_reserve_move = v5.891: the country named in coin (three letter ISO code, for example POL, CHN, TUR) changes its official gold by the threshold in tonnes or more in one monthly release, buying or selling (IMF file or a national release); gold_cb_selling = v5.891: the central banks that report to the IMF, added together, sold more gold than they bought in the latest month (no threshold needed); coin is GOLD; gold_crypto_verdict = v5.892, the bull alert: the crypto verdict on owlchart.com/gold.html moves to STARTING or RECEIVING, the day gold money starts landing in crypto (no threshold needed); coin is BTC; nvda_carv_move = v5.898: Nvidia moves by the threshold percent or more against yesterday's close (for example 3) and the alert tells what CARV is doing at that moment; coin is CARV; carv_decouple = v5.898: CARV lets go of Nvidia: the 30 day link on owlchart.com/nvidia.html drops under 0.30, or CARV is up 3% or more on a day Nvidia is down (no threshold needed); coin is CARV; nvda_after_hours = v5.898: Nvidia's pre market or after hours price is the threshold percent or more away from the close (for example 3), for traders of CARV, which trades all night; coin is NVDA; nvda_move = v5.896: Nvidia moves by the threshold percent or more against yesterday's close, up or down (for example 3; a negative number fires only on a fall that size); coin is NVDA; nvda_ai_verdict = v5.896: the AI crypto verdict on owlchart.com/nvidia.html moves to STARTING or RECEIVING, the day Nvidia money starts reaching the AI tokens (no threshold needed); coin is CARV; nvda_receiver = v5.896: the market named in coin (AMD, AVGO, TSM, SMH, QQQ, XLU, SGOV, GOLD, DXY, BTC, ETH, CARV, FET, TAO, VIRTUAL, AIB for the AI token basket and the other rows of owlchart.com/nvidia.html) turns to RECEIVING on the Nvidia Hub (no threshold needed); nvda_earnings = v5.896: the next Nvidia results are the threshold in days away or fewer (for example 2); coin is NVDA; inflation_nowcast = v5.897: the OwlChart nowcast of the coming US CPI, month on month, is at the threshold percent or above (for example 0.3; a negative number fires at that level or below); coin is CPI; inflation_cooling = v5.897: owlchart.com/inflation.html turns to COOLING against the last official CPI print (no threshold needed); coin is CPI; inflation_petrol = v5.897: the US weekly pump price of petrol is at or below the threshold in dollars a gallon (for example 3.8); coin is GAS; inflation_cpi_out = v5.897: a new official CPI month reaches owlchart.com/inflation.html, with the number and the OwlChart nowcast beside it (no threshold needed); coin is CPI; gold_move = v5.890: gold futures move by the threshold percent or more against yesterday's close, up or down (for example 2; a negative number fires only on a fall that size); coin is GOLD; gold_receiver = v5.890: the market named in coin (BTC, ETH, DXY, TNX, CL, GSPC and the other rows of owlchart.com/gold.html) turns to RECEIVING on the Gold Hub, meaning it rose on most of the days gold fell hard (no threshold needed); gold_btc_ratio = v5.890: one Bitcoin costs the threshold in ounces of gold or more (for example 20; a negative number fires at that many ounces or fewer); coin is BTC; gold_token_mint = v5.890: the supply of a gold token (coin = PAXG or XAUT) changes by the threshold in ounces or more in a day, a mint or a burn, read from the Ethereum contract; kimchi_premium = v5.887: the Upbit KRW price of CARV, in dollars, trades above the global price by the threshold percent or more (for example 5; a negative number fires when it is that far below); coin must be CARV; korea_volume = v5.887: the 24 hour CARV volume on Upbit plus Bithumb reaches the threshold times its own 7 day average (for example 2 for double); coin must be CARV; stable_depeg = v5.853: USDT or USDC (coin) trades more than 0.5% away from one dollar on a dollar venue for 5 minutes (no threshold needed). When it fires it shows in check_alerts and, if a webhook is given (Discord, Slack, Zapier, Make, n8n or any https hook), a message is sent there too. One-shot. Up to 10 active alerts per member.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "coin": "<coin>",
      "type": "<type>"
    },
    "name": "create_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinYesCoin ticker, e.g. BTC, WLFI
noteNo
typeYes
thresholdNoDollars for price alerts, percent for oi_change and funding_extreme
webhook_urlNoOptional https webhook for delivery

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "price_above",
      -  "price_below",
      -  "oi_change",
      -  "magnet_hit",
      -  "funding_extreme",
      -  "etf_flip",
      -  "stablecoin_mint",
      -  "large_transfer",
      -  "reg_keyword",
      -  "stable_print",
      -  "stable_pulse",
      -  "wlfi_buyback_surge",
      -  "wlfi_buyback_stop",
      -  "gold_reserve_move",
      -  "gold_cb_selling",
      -  "gold_crypto_verdict",
      -  "gold_move",
      -  "gold_receiver",
      -  "gold_btc_ratio",
      -  "gold_token_mint",
      -  "kimchi_premium",
      -  "korea_volume",
      -  "stable_depeg"
      -]New value: +[
      +  "price_above",
      +  "price_below",
      +  "oi_change",
      +  "magnet_hit",
      +  "funding_extreme",
      +  "etf_flip",
      +  "stablecoin_mint",
      +  "large_transfer",
      +  "reg_keyword",
      +  "stable_print",
      +  "stable_pulse",
      +  "wlfi_buyback_surge",
      +  "wlfi_buyback_stop",
      +  "gold_reserve_move",
      +  "gold_cb_selling",
      +  "gold_crypto_verdict",
      +  "nvda_carv_move",
      +  "carv_decouple",
      +  "nvda_after_hours",
      +  "nvda_move",
      +  "nvda_ai_verdict",
      +  "nvda_receiver",
      +  "nvda_earnings",
      +  "inflation_nowcast",
      +  "inflation_cooling",
      +  "inflation_petrol",
      +  "inflation_cpi_out",
      +  "gold_move",
      +  "gold_receiver",
      +  "gold_btc_ratio",
      +  "gold_token_mint",
      +  "kimchi_premium",
      +  "korea_volume",
      +  "stable_depeg"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "price_above",
      -  "price_below",
      -  "oi_change",
      -  "magnet_hit",
      -  "funding_extreme",
      -  "etf_flip",
      -  "stablecoin_mint",
      -  "large_transfer",
      -  "reg_keyword",
      -  "stable_print",
      -  "stable_pulse",
      -  "wlfi_buyback_surge",
      -  "wlfi_buyback_stop",
      -  "kimchi_premium",
      -  "korea_volume",
      -  "stable_depeg"
      -]New value: +[
      +  "price_above",
      +  "price_below",
      +  "oi_change",
      +  "magnet_hit",
      +  "funding_extreme",
      +  "etf_flip",
      +  "stablecoin_mint",
      +  "large_transfer",
      +  "reg_keyword",
      +  "stable_print",
      +  "stable_pulse",
      +  "wlfi_buyback_surge",
      +  "wlfi_buyback_stop",
      +  "gold_reserve_move",
      +  "gold_cb_selling",
      +  "gold_crypto_verdict",
      +  "gold_move",
      +  "gold_receiver",
      +  "gold_btc_ratio",
      +  "gold_token_mint",
      +  "kimchi_premium",
      +  "korea_volume",
      +  "stable_depeg"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "price_above",
      -  "price_below",
      -  "oi_change",
      -  "magnet_hit",
      -  "funding_extreme",
      -  "etf_flip",
      -  "stablecoin_mint",
      -  "large_transfer",
      -  "reg_keyword",
      -  "stable_print",
      -  "stable_pulse",
      -  "stable_depeg"
      -]New value: +[
      +  "price_above",
      +  "price_below",
      +  "oi_change",
      +  "magnet_hit",
      +  "funding_extreme",
      +  "etf_flip",
      +  "stablecoin_mint",
      +  "large_transfer",
      +  "reg_keyword",
      +  "stable_print",
      +  "stable_pulse",
      +  "wlfi_buyback_surge",
      +  "wlfi_buyback_stop",
      +  "kimchi_premium",
      +  "korea_volume",
      +  "stable_depeg"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "price_above",
      -  "price_below",
      -  "oi_change",
      -  "magnet_hit",
      -  "funding_extreme",
      -  "etf_flip",
      -  "stablecoin_mint",
      -  "large_transfer",
      -  "reg_keyword"
      -]New value: +[
      +  "price_above",
      +  "price_below",
      +  "oi_change",
      +  "magnet_hit",
      +  "funding_extreme",
      +  "etf_flip",
      +  "stablecoin_mint",
      +  "large_transfer",
      +  "reg_keyword",
      +  "stable_print",
      +  "stable_pulse",
      +  "stable_depeg"
      +]
  5. Changed1 schema field changed
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "price_above",
      -  "price_below",
      -  "oi_change",
      -  "magnet_hit",
      -  "funding_extreme",
      -  "etf_flip",
      -  "stablecoin_mint"
      -]New value: +[
      +  "price_above",
      +  "price_below",
      +  "oi_change",
      +  "magnet_hit",
      +  "funding_extreme",
      +  "etf_flip",
      +  "stablecoin_mint",
      +  "large_transfer",
      +  "reg_keyword"
      +]
  6. Changed1 schema field changed
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "price_above",
      -  "price_below",
      -  "oi_change",
      -  "magnet_hit",
      -  "funding_extreme",
      -  "etf_flip"
      -]New value: +[
      +  "price_above",
      +  "price_below",
      +  "oi_change",
      +  "magnet_hit",
      +  "funding_extreme",
      +  "etf_flip",
      +  "stablecoin_mint"
      +]
  7. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only say this is a non-read-only, non-idempotent create; the description adds the behavior that actually matters: minute-level check cadence, one-shot firing, a cap of 10 active alerts per member, webhook delivery to Discord/Slack/Zapier/Make/n8n/any https hook, and that firings surface via check_alerts. It also discloses external data dependencies (Ethereum contracts, IMF file, issuer treasury) that the annotations' openWorldHint=false does not convey.

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

Conciseness3/5

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

Nearly every sentence carries load, but it is delivered as a single undifferentiated wall of text with version stamps (v5.853, v5.896) that add noise rather than meaning. Semicolon-separated type definitions in one paragraph force an agent to parse linearly instead of scanning; the same content as a bulleted or sectioned list would be far more usable.

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 35-value enum with no per-value schema descriptions, this covers all variants, coin constraints, threshold semantics, delivery channel and the active-alert cap — enough to call it correctly. The one gap is the return side: with no output schema and no statement of what create_alert hands back (alert id for later delete_alert?), the agent must guess how to reference the alert it just created.

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

Parameters5/5

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

The schema covers two of five parameters with descriptions and leaves note and type effectively bare, so the description carries real weight — and it does, by defining threshold units per type (dollars, percent, tonnes, ounces, millions of dollars, days) and coin values per type. It also explains that note supplies the keyword for reg_keyword, a constraint absent from 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?

Opens with a specific verb and resource: "Sets an alert on OwlChart data, checked every minute." It distinguishes itself from the sibling check_alerts by naming it ('shows in check_alerts') and enumerating exactly which conditions can be alerted, so an agent can decide whether this tool or a read-only sibling fits.

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?

Per-type guidance is exhaustive: which types need no threshold (magnet_hit, stable_pulse, gold_cb_selling), which require a specific coin (coin must be WLFI/CARV/NVDA), and how sign of threshold changes firing behavior. What's absent is explicit routing against non-alert siblings (e.g. get_funding_rates, get_gold) — the description never says to use those for one-off inspection instead of creating an alert.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources