Skip to main content
Glama

OwlChart

by com.owlchart
OverviewDiscussionsAdmin

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). 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.

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"
-]New value: +[
+  "price_above",
+  "price_below",
+  "oi_change",
+  "magnet_hit",
+  "funding_extreme",
+  "etf_flip",
+  "stablecoin_mint",
+  "large_transfer",
+  "reg_keyword"
+]
  2. 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"
+]
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare the safety profile (readOnly=false, idempotent=false, destructive=false); the description adds substantive behavior the annotations cannot convey: one-minute checking, one-shot firing, the 10-alert cap, and webhook delivery to Discord/Slack/Zapier/Make/n8n or any https hook.

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?

Dense but front-loaded, with purpose stated first and then the type catalog. Every clause carries necessary information, though the semicolon-delimited wall of type definitions would scan better as a list.

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?

For a 5-parameter creation tool with no output schema, the description covers trigger semantics, delivery, limits, and per-type parameter meaning, so nothing essential to correct invocation is missing.

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?

With only 60% schema coverage, the description compensates heavily: it defines what 'threshold' means per type (dollars, percent, millions, or unused for magnet_hit/reg_keyword), when it may be negative, that 'coin' is ignored for stablecoin_mint and reg_keyword, that 'note' is the keyword for reg_keyword, and that large_transfer takes a token hub id — far beyond the terse schema descriptions.

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 opening sentence states a specific verb and resource ('Sets an alert on OwlChart data') plus the polling cadence, which immediately distinguishes it from check_alerts, list_alerts and delete_alert. An agent can identify this as the alert-creation tool without opening the 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?

It explains the operational context (fires when condition met, one-shot, up to 10 active alerts per member, optional webhook delivery) and points to check_alerts for observing results. It stops short of explicitly routing the agent to siblings (e.g. 'use delete_alert to cancel'), but the surrounding context is clear.

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

All OwlChart toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources