Skip to main content
Glama

alert_link

Destructive

Prepare a price, indicator, chart-drawing, news, calendar or Founder whale-group alert and get a link that sets it in Basis in one click. Use it whenever the person wants to be told when something happens -- a level breaks, RSI crosses 70, price crosses a trend line, a high-impact ETF headline lands, or an event approaches. Pass exactly one of price, conditions, drawingId or eventTrigger. Give the URL as a link and say in one line what it watches. Nothing is armed until they open it and confirm. Market alerts can run in an open tab; background and event alerts require a signed-in Basis account. The link lasts seven days.

Input Schema

NameRequiredDescriptionDefault
nameNoWhat the person sees when it fires. Chosen for you if omitted.
whenNoWith price. Omit to pick the crossing from where price is now.
matchNoHow conditions combine. Default all.
priceNoShorthand for a price-level alert.
marketNo
symbolNoe.g. BTCUSDT. Defaults to the chart you are building.
messageNoOptional note carried into the notification.
exchangeNo
drawingIdNoID returned by drawing_add. Supports horizontalLine, horizontalRay, trendLine, ray and extendedLine.
frequencyNoDefault once: fires, then switches itself off.
timeframeNoBars the alert is checked on. Free presets: 1m, 3m, 5m, 10m, 15m, 30m, 1h, 2h, 4h, 6h, 8h, 12h, 1d, 3d, 1w, 1M. Founder-only custom intervals: 1–1440 minutes (17m), 1–168 hours (7h), 1–365 days (2d).
conditionsNoInstead of price. Each {left, operator, right}. An operand is a number, a price field ("close"), an indicator name ("rsi", "ema50"), or {"type":"indicator","studyId":"macd","plotKey":"histogram","params":{}}. rising and falling need no right; changeUpPercent and changeDownPercent take a percent.
eventTriggerNoInstead of market conditions. A news, Basis calendar or Founder whale-group event filter.
cooldownMinutesNoWith frequency cooldown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • changedInput schema / properties / eventTrigger / description
      Previous value: -"Instead of market conditions. A news or Basis calendar event filter."New value: +"Instead of market conditions. A news, Basis calendar or Founder whale-group event filter."
    • addedInput schema / properties / eventTrigger / properties / actions
      Added value: +{
      +  "items": {
      +    "enum": [
      +      "opened",
      +      "added",
      +      "reduced",
      +      "closed",
      +      "flipped"
      +    ],
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / eventTrigger / properties / coins
      Added value: +{
      +  "description": "Whale: exact Hyperliquid coins, preserving HIP-3 prefixes.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / eventTrigger / properties / minUsd
      Added value: +{
      +  "description": "Whale minimum absolute position change notional; default 50000.",
      +  "type": "number"
      +}
    • addedInput schema / properties / eventTrigger / properties / side
      Added value: +{
      +  "enum": [
      +    "any",
      +    "long",
      +    "short"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / eventTrigger / properties / together
      Added value: +{
      +  "description": "Distinct accounts moving on the same coin and side. Default 1.",
      +  "type": "integer"
      +}
    • changedInput schema / properties / eventTrigger / properties / type / enum
      Previous value: -[
      -  "news",
      -  "calendar"
      -]New value: +[
      +  "news",
      +  "calendar",
      +  "whale"
      +]
    • addedInput schema / properties / eventTrigger / properties / whales
      Added value: +{
      +  "description": "Founders only: opaque account IDs from founder_whales or founder_whale_research.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 6,
      +  "minItems": 1,
      +  "type": "array"
      +}
    • addedInput schema / properties / eventTrigger / properties / windowMinutes
      Added value: +{
      +  "description": "Whale concurrence window, 5–1440; default 60.",
      +  "type": "integer"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / timeframe / description
      Previous value: -"Bars the alert is checked on, e.g. 15m, 1h, 4h. One of 1m, 3m, 5m, 10m, 15m, 30m, 1h, 2h, 4h, 6h, 8h, 12h, 1d, 3d, 1w, 1M."New value: +"Bars the alert is checked on. Free presets: 1m, 3m, 5m, 10m, 15m, 30m, 1h, 2h, 4h, 6h, 8h, 12h, 1d, 3d, 1w, 1M. Founder-only custom intervals: 1–1440 minutes (17m), 1–168 hours (7h), 1–365 days (2d)."
  3. Changed2 schema fields changed
    • addedInput schema / properties / drawingId
      Added value: +{
      +  "description": "ID returned by drawing_add. Supports horizontalLine, horizontalRay, trendLine, ray and extendedLine.",
      +  "type": "string"
      +}
    • addedInput schema / properties / eventTrigger
      Added value: +{
      +  "description": "Instead of market conditions. A news or Basis calendar event filter.",
      +  "properties": {
      +    "assets": {
      +      "description": "News asset symbols, e.g. BTC, ETH.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "categories": {
      +      "items": {
      +        "enum": [
      +          "macro",
      +          "network",
      +          "derivatives"
      +        ],
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "keywordMode": {
      +      "enum": [
      +        "all",
      +        "any"
      +      ],
      +      "type": "string"
      +    },
      +    "keywords": {
      +      "description": "News: literal phrases in title or summary.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "leadMinutes": {
      +      "description": "Calendar: notify this many minutes before the event.",
      +      "type": "number"
      +    },
      +    "minImpact": {
      +      "description": "News: 0-100 score. Calendar: low, medium or high."
      +    },
      +    "sources": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "titleContains": {
      +      "description": "Calendar: literal title/description phrases.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "titleMode": {
      +      "enum": [
      +        "all",
      +        "any"
      +      ],
      +      "type": "string"
      +    },
      +    "topics": {
      +      "items": {
      +        "enum": [
      +          "regulation",
      +          "macro",
      +          "security",
      +          "etf",
      +          "stablecoins",
      +          "exchanges",
      +          "defi",
      +          "institutions",
      +          "mining",
      +          "markets"
      +        ],
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "type": {
      +      "enum": [
      +        "news",
      +        "calendar"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "type"
      +  ],
      +  "type": "object"
      +}
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: nothing is armed until the link is opened and confirmed, market alerts can run in an open tab while background/event alerts need a signed-in Basis account, and the link expires after seven days. It does not reconcile this with destructiveHint=true, leaving a mild gap about server-side state created at prepare time.

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?

Five front-loaded sentences: purpose, usage, the exclusivity rule, the delivery instruction, then behavioral caveats. Dense but every sentence carries information an agent needs for this 14-parameter tool.

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?

Despite 14 parameters, nested objects and no output schema, the description covers selection logic, the returned link and expected one-line summary, the confirmation gate, and account/expiry constraints. Nothing essential for correct invocation is missing.

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 description coverage is already 86%, so the baseline is 3. The description adds a genuinely useful cross-parameter constraint absent from the schema: pass exactly one of price, conditions, drawingId or eventTrigger, plus notes on frequency defaults and Founder-only custom timeframes.

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 concrete verb and resource: prepare an alert (price, indicator, drawing, news, calendar, whale-group) and return a one-click link. The enumerated alert families let an agent tell it apart from siblings like drawing_add (which supplies drawingId) or news_recent (which merely reads news).

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?

Gives explicit when-to-use guidance with concrete trigger examples (level breaks, RSI crosses 70, high-impact ETF headline) and states the exactly-one-of price/conditions/drawingId/eventTrigger routing rule. It does not, however, say when NOT to use it or name a sibling to prefer for adjacent needs.

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