Skip to main content
Glama
Tickerbot MCP Server

Tickerbot MCP Server

Official
by tickerbot

tickerbot_subscribe_ticker

Creates an alert that fires when a single ticker starts matching a condition, delivered via webhook, Discord, mobile push, or in-app feed on realtime, hourly, or NYSE-open cadence.

Instructions

Gets you an alert by webhook each time one ticker starts matching a condition. Webhooks need a paid plan (Free has no webhook slots). Omit target_url for in-app delivery.

Input Schema

NameRequiredDescriptionDefault
qNoWHERE-clause fragment using signal names from the catalog, the same grammar as `/v2/scan`. Custom signals are expanded and frozen in at creation.
nameNoDisplay name, up to 80 characters. Defaults to `<TICKER>: ` plus the first 40 characters of `q`.
selectNoWhat each delivery carries. Omitted: the scan default row (ticker, name, asset_class, asset_type, price, change_1d_pct, gap_pct, relative_volume, market_cap) plus every signal used in `q`. A list of signal names: exactly those, `ticker` always included. Each must be a real signal; unknown ones are rejected at creation. `*` and expressions are a 400: a delivery lists up to 100 matches, so name the signals.
tickerYesOne ticker. For several, use Subscribe to a scan with `q="ticker IN ('NVDA','AAPL') AND (…)"`. Case-insensitive. Equities are bare symbols (`NVDA`); every other class carries a prefix: rates (`R:SOFR`), crypto (`X:BTCUSD`), fx (`X:EURUSD`). Bare `BTC`/`ETH` are US-listed ETFs, not spot crypto. See Tickers.
cadenceNoHow often to evaluate: `realtime` (the default) is checked each time the data refreshes, about once a minute; `hourly` and `nyse_open` are checked on that schedule. Values: realtime: Checked each time the data refreshes: about once a minute from 4 AM to 8 PM ET for stocks and ETFs, every minute around the clock for crypto and FX, and as each event lands for event webhooks. Fires when a ticker starts matching. The default. hourly: Checked once an hour. nyse_open: Checked once a day, at the 9:30 AM ET open, on NYSE trading days.
channelNoDelivery channel: `webhook` (POST to `target_url`), `discord` (an embed at `discord_url`), `in_app` (the dashboard only) or `mobile_push` (to `device_id`). Inferred when omitted: `discord` if `discord_url` is set, else `mobile_push` if `device_id` is set, else `webhook` if `target_url` is set, else `in_app`. See Delivery channels. Values: webhook: POST the payload to an HTTPS endpoint you own, signed with `X-Tickerbot-Signature`. discord: Post to a Discord channel via its webhook URL. Delivered as a Discord embed, never HMAC-signed: the URL is itself the credential. in_app: Deliver to the in-app feed. No external receiver, so nothing to validate and no `test_url`. mobile_push: Push to a registered device. Requires a `device_id` from Register a device.
device_idNoOnly with `channel=mobile_push`. Device to notify, from `POST /v2/devices/register`. An unknown id is a 400 `device_not_found`.
target_urlNoOnly with `channel=webhook`. HTTPS URL each delivery is POSTed to.
discord_urlNoOnly with `channel=discord`. Discord incoming-webhook URL (`https://discord.com/api/webhooks/…`). Stored as a posting credential: the create response echoes it back under `channel_config`, but every later read (list, get, deliveries) strips it and sets `channel_config_present: true` instead.

Output Schema

NameRequiredDescriptionDefault
qYesThe stored predicate. Custom signals appear expanded: the SQL is frozen at creation. On an event webhook, the whole filter (the event's fields and the ticker's signals); `null` when it fires on every event. On a news webhook, the Query news `q`, or `null`.
idYesThe webhook id (`wh_…`), the handle for every other call on this record.
dirYesSort direction for those lists: `desc` unless you chose one. `null` on event and news webhooks. One of: `asc`, `desc`.
kindNoEvent webhooks only: the kinds subscribed. One of: `earnings`, `filing`, `dividend`, `split`, `insider`, `analyst`, `estimate_revision`.
nameYesYour label for the subscription.
_metaNoReturned on create only, and only when the rule or `select` named a signal under its pre-2026-09-07 spelling: `deprecated_signals` lists each one (`requested`, `use`, `note`). The stored rule carries the current name.
as_ofYesServer time this response was assembled (ISO 8601); on an as-of read, the instant you asked for (As-of).
orderYesSort signal for each delivery's match lists: `market_cap` unless you chose one, so a broad alert lists the same top 100 names each time. `null` on event and news webhooks.
searchNoNews webhooks only: the full-text search it fires on, or `null`.
selectYesThe signals each delivered match carries, after `ticker`; `null` means the scan default row plus the signals the rule uses in `q` and `order`. On a news webhook, the article fields each delivered article carries.
statusYesWhether it is live. `disabled_reason` says why a webhook is disabled. One of: `active`, `disabled`.
tickerNoEvent and news webhooks only: the symbols it is scoped to, or `null` for the universe or the whole market.
cadenceNoScan, ticker and signal webhooks only: how often the trigger is evaluated. Event and news webhooks fire as rows land. One of: `realtime`, `hourly`, `nyse_open`.
channelYesWhere deliveries go. One of: `webhook`, `discord`, `in_app`, `mobile_push`.
test_urlNoReturned on create only, when the channel delivers outside the dashboard: the path of `POST /v2/webhooks/{webhook}/test` for this record.
universeYesUniverse the trigger is scoped to, or `null` for the whole market.
created_atYesCreation timestamp (epoch seconds).
last_errorNoThe last evaluation error; `null` on a healthy hook. The answer to "why is my webhook not firing?".
last_firedYesWhen a delivery last went out (epoch seconds); `null` if it never has.
target_urlYesYour HTTPS endpoint; `null` on every channel except `webhook`.
updated_atYesLast modification timestamp (epoch seconds).
_advisoriesNoPresent only when the response carried a warning: `deprecated` (since, sunset_on, successor, warning; on a deprecated tool, successor names the tool to call), `rate_limit` (warning, retry_after_seconds, limit, remaining, reset_epoch_s) or `monthly_quota` (warning, limit, remaining, reset_epoch_s).
disabled_atNoAfter an `evaluation_failure`, `plan_downgrade` or `subscription_canceled`: when it was disabled (epoch seconds).
next_eval_atNoWhen the evaluator will next consider this subscription (epoch seconds).
failing_sinceNoWhen the current failure streak began (epoch seconds); `null` while deliveries are succeeding.
min_relevanceNoNews webhooks only: the least `relevance` a scoped ticker needs, or `null`.
channel_configYesReturned on create only: the channel-specific delivery settings as stored (e.g. the Discord URL, the device id).
last_match_setNoScan, ticker and signal webhooks only: tickers matching at the last evaluation, the set the next run is diffed against, which is what makes firing edge-triggered.
signing_secretYesReturned on create only, and shown once. HMAC key for verifying the `X-Tickerbot-Signature` header on deliveries.
disabled_reasonNoDisabled webhooks only: why it was turned off. Turn it back on with `PATCH /v2/webhooks/{webhook}` and `enabled: true`. One of: `user_disabled`, `delivery_failure`, `evaluation_failure`, `plan_downgrade`, `subscription_canceled`.
last_success_atNoWhen a delivery last reached your endpoint, in epoch seconds (`created_at` until the first one does).
last_evaluated_atNoScan, ticker and signal webhooks only: when it was last evaluated (epoch seconds); `null` until the first run.
last_eval_error_atNoWhen the last evaluation error happened (epoch seconds); `null` on a healthy hook.
disabled_last_errorNoAfter a `delivery_failure` or `evaluation_failure`: the error that disabled it; `null` when your endpoint answered with an HTTP status (see `disabled_last_status_code`).
subscription_originYesWhich subscribe route created it: `type` (`ticker`/`signal`/`scan`/`event`/`news`), its `ref` and the `condition` in display form.
consecutive_failuresNoDeliveries in a row that failed after the full retry ladder; resets on any success. Informational: a webhook is disabled when deliveries have kept failing for 72 hours (since `failing_since`) with none getting through, not on a count.
disabled_explanationNoAfter an `evaluation_failure`: what changed and what to use instead, for example the new name of a renamed signal.
disable_email_sent_atNoWhen we emailed you about the disable (epoch seconds).
channel_config_presentNoDiscord and mobile-push webhooks: `true` when delivery settings are stored. The Discord URL itself is never returned after create.
disabled_last_status_codeNoAfter a `delivery_failure`: the HTTP status your endpoint last returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed17 schema fields changedv0.4.1
    • addedInput schema / anyOf
      Added value: +[
      +  {
      +    "required": [
      +      "q"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "condition"
      +    ]
      +  }
      +]
    • changedInput schema / properties / cadence / description
      Previous value: -"Evaluation cadence. Default realtime; hourly/nyse_open throttle. (`1m` accepted as a deprecated alias of realtime.)"New value: +"How often to evaluate: `realtime` (the default) is checked each time the data refreshes, about once a minute; `hourly` and `nyse_open` are checked on that schedule. Values: realtime: Checked each time the data refreshes: about once a minute from 4 AM to 8 PM ET for stocks and ETFs, every minute around the clock for crypto and FX, and as each event lands for event webhooks. Fires when a ticker starts matching. The default. hourly: Checked once an hour. nyse_open: Checked once a day, at the 9:30 AM ET open, on NYSE trading days."
    • removedInput schema / properties / cadence / enum
      Removed value: -[
      -  "realtime",
      -  "hourly",
      -  "nyse_open"
      -]
    • addedInput schema / properties / cadence / pattern
      Added value: +"^\\s*([rR][eE][aA][lL][tT][iI][mM][eE]|[hH][oO][uU][rR][lL][yY]|[nN][yY][sS][eE]_[oO][pP][eE][nN])\\s*$"
    • changedInput schema / properties / channel / description
      Previous value: -"Delivery channel: `webhook` (POST to target_url), `discord` (embed to discord_url), `mobile_push` (to a registered device), or `in_app` (dashboard only). Inferred from the URL you pass if omitted."New value: +"Delivery channel: `webhook` (POST to `target_url`), `discord` (an embed at `discord_url`), `in_app` (the dashboard only) or `mobile_push` (to `device_id`). Inferred when omitted: `discord` if `discord_url` is set, else `mobile_push` if `device_id` is set, else `webhook` if `target_url` is set, else `in_app`. See Delivery channels. Values: webhook: POST the payload to an HTTPS endpoint you own, signed with `X-Tickerbot-Signature`. discord: Post to a Discord channel via its webhook URL. Delivered as a Discord embed, never HMAC-signed: the URL is itself the credential. in_app: Deliver to the in-app feed. No external receiver, so nothing to validate and no `test_url`. mobile_push: Push to a registered device. Requires a `device_id` from Register a device."
    • removedInput schema / properties / channel / enum
      Removed value: -[
      -  "webhook",
      -  "discord",
      -  "in_app",
      -  "mobile_push"
      -]
    • addedInput schema / properties / channel / pattern
      Added value: +"^\\s*([wW][eE][bB][hH][oO][oO][kK]|[dD][iI][sS][cC][oO][rR][dD]|[iI][nN]_[aA][pP][pP]|[mM][oO][bB][iI][lL][eE]_[pP][uU][sS][hH])\\s*$"
    • removedInput schema / properties / condition
      Removed value: -{
      -  "description": "SQL WHERE fragment evaluated for this ticker.",
      -  "type": "string"
      -}
    • changedInput schema / properties / device_id / description
      Previous value: -"Registered device id from the mobile app. Required when channel is \"mobile_push\"."New value: +"Only with `channel=mobile_push`. Device to notify, from `POST /v2/devices/register`. An unknown id is a 400 `device_not_found`."
    • changedInput schema / properties / discord_url / description
      Previous value: -"Discord incoming-webhook URL (https://discord.com/api/webhooks/…). Required when channel is \"discord\"."New value: +"Only with `channel=discord`. Discord incoming-webhook URL (`https://discord.com/api/webhooks/…`). Stored as a posting credential: the create response echoes it back under `channel_config`, but every later read (list, get, deliveries) strips it and sets `channel_config_present: true` instead."
    • changedInput schema / properties / name / description
      Previous value: -"Human-readable label."New value: +"Display name, up to 80 characters. Defaults to `<TICKER>: ` plus the first 40 characters of `q`."
    • addedInput schema / properties / q
      Added value: +{
      +  "description": "WHERE-clause fragment using signal names from the catalog, the same grammar as `/v2/scan`. Custom signals are expanded and frozen in at creation.",
      +  "type": "string"
      +}
    • addedInput schema / properties / select
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  ],
      +  "description": "What each delivery carries. Omitted: the scan default row (ticker, name, asset_class, asset_type, price, change_1d_pct, gap_pct, relative_volume, market_cap) plus every signal used in `q`. A list of signal names: exactly those, `ticker` always included. Each must be a real signal; unknown ones are rejected at creation. `*` and expressions are a 400: a delivery lists up to 100 matches, so name the signals."
      +}
    • changedInput schema / properties / target_url / description
      Previous value: -"Optional https URL for the `webhook` channel; omit for in-app."New value: +"Only with `channel=webhook`. HTTPS URL each delivery is POSTed to."
    • changedInput schema / properties / ticker / description
      Previous value: -"Symbol."New value: +"One ticker. For several, use Subscribe to a scan with `q=\"ticker IN ('NVDA','AAPL') AND (…)\"`. Case-insensitive. Equities are bare symbols (`NVDA`); every other class carries a prefix: rates (`R:SOFR`), crypto (`X:BTCUSD`), fx (`X:EURUSD`). Bare `BTC`/`ETH` are US-listed ETFs, not spot crypto. See Tickers."
    • changedInput schema / required
      Previous value: -[
      -  "ticker",
      -  "condition"
      -]New value: +[
      +  "ticker"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "_advisories": {
      +      "description": "Present only when the response carried a warning: `deprecated` (since, sunset_on, successor, warning; on a deprecated tool, successor names the tool to call), `rate_limit` (warning, retry_after_seconds, limit, remaining, reset_epoch_s) or `monthly_quota` (warning, limit, remaining, reset_epoch_s).",
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "_meta": {
      +      "description": "Returned on create only, and only when the rule or `select` named a signal under its pre-2026-09-07 spelling: `deprecated_signals` lists each one (`requested`, `use`, `note`). The stored rule carries the current name."
      +    },
      +    "as_of": {
      +      "description": "Server time this response was assembled (ISO 8601); on an as-of read, the instant you asked for (As-of).",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "cadence": {
      +      "description": "Scan, ticker and signal webhooks only: how often the trigger is evaluated. Event and news webhooks fire as rows land. One of: `realtime`, `hourly`, `nyse_open`.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "channel": {
      +      "description": "Where deliveries go. One of: `webhook`, `discord`, `in_app`, `mobile_push`.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "channel_config": {
      +      "description": "Returned on create only: the channel-specific delivery settings as stored (e.g. the Discord URL, the device id)."
      +    },
      +    "channel_config_present": {
      +      "description": "Discord and mobile-push webhooks: `true` when delivery settings are stored. The Discord URL itself is never returned after create."
      +    },
      +    "consecutive_failures": {
      +      "description": "Deliveries in a row that failed after the full retry ladder; resets on any success. Informational: a webhook is disabled when deliveries have kept failing for 72 hours (since `failing_since`) with none getting through, not on a count."
      +    },
      +    "created_at": {
      +      "description": "Creation timestamp (epoch seconds).",
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "dir": {
      +      "description": "Sort direction for those lists: `desc` unless you chose one. `null` on event and news webhooks. One of: `asc`, `desc`.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "disable_email_sent_at": {
      +      "description": "When we emailed you about the disable (epoch seconds)."
      +    },
      +    "disabled_at": {
      +      "description": "After an `evaluation_failure`, `plan_downgrade` or `subscription_canceled`: when it was disabled (epoch seconds)."
      +    },
      +    "disabled_explanation": {
      +      "description": "After an `evaluation_failure`: what changed and what to use instead, for example the new name of a renamed signal."
      +    },
      +    "disabled_last_error": {
      +      "description": "After a `delivery_failure` or `evaluation_failure`: the error that disabled it; `null` when your endpoint answered with an HTTP status (see `disabled_last_status_code`)."
      +    },
      +    "disabled_last_status_code": {
      +      "description": "After a `delivery_failure`: the HTTP status your endpoint last returned."
      +    },
      +    "disabled_reason": {
      +      "description": "Disabled webhooks only: why it was turned off. Turn it back on with `PATCH /v2/webhooks/{webhook}` and `enabled: true`. One of: `user_disabled`, `delivery_failure`, `evaluation_failure`, `plan_downgrade`, `subscription_canceled`."
      +    },
      +    "failing_since": {
      +      "description": "When the current failure streak began (epoch seconds); `null` while deliveries are succeeding."
      +    },
      +    "id": {
      +      "description": "The webhook id (`wh_…`), the handle for every other call on this record.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "kind": {
      +      "description": "Event webhooks only: the kinds subscribed. One of: `earnings`, `filing`, `dividend`, `split`, `insider`, `analyst`, `estimate_revision`."
      +    },
      +    "last_error": {
      +      "description": "The last evaluation error; `null` on a healthy hook. The answer to \"why is my webhook not firing?\"."
      +    },
      +    "last_eval_error_at": {
      +      "description": "When the last evaluation error happened (epoch seconds); `null` on a healthy hook."
      +    },
      +    "last_evaluated_at": {
      +      "description": "Scan, ticker and signal webhooks only: when it was last evaluated (epoch seconds); `null` until the first run.",
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "last_fired": {
      +      "description": "When a delivery last went out (epoch seconds); `null` if it never has."
      +    },
      +    "last_match_set": {
      +      "description": "Scan, ticker and signal webhooks only: tickers matching at the last evaluation, the set the next run is diffed against, which is what makes firing edge-triggered.",
      +      "type": [
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "last_success_at": {
      +      "description": "When a delivery last reached your endpoint, in epoch seconds (`created_at` until the first one does).",
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "min_relevance": {
      +      "description": "News webhooks only: the least `relevance` a scoped ticker needs, or `null`."
      +    },
      +    "name": {
      +      "description": "Your label for the subscription.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "next_eval_at": {
      +      "description": "When the evaluator will next consider this subscription (epoch seconds).",
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "order": {
      +      "description": "Sort signal for each delivery's match lists: `market_cap` unless you chose one, so a broad alert lists the same top 100 names each time. `null` on event and news webhooks.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "q": {
      +      "description": "The stored predicate. Custom signals appear expanded: the SQL is frozen at creation. On an event webhook, the whole filter (the event's fields and the ticker's signals); `null` when it fires on every event. On a news webhook, the Query news `q`, or `null`.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "search": {
      +      "description": "News webhooks only: the full-text search it fires on, or `null`."
      +    },
      +    "select": {
      +      "description": "The signals each delivered match carries, after `ticker`; `null` means the scan default row plus the signals the rule uses in `q` and `order`. On a news webhook, the article fields each delivered article carries."
      +    },
      +    "signing_secret": {
      +      "description": "Returned on create only, and shown once. HMAC key for verifying the `X-Tickerbot-Signature` header on deliveries."
      +    },
      +    "status": {
      +      "description": "Whether it is live. `disabled_reason` says why a webhook is disabled. One of: `active`, `disabled`.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "subscription_origin": {
      +      "description": "Which subscribe route created it: `type` (`ticker`/`signal`/`scan`/`event`/`news`), its `ref` and the `condition` in display form.",
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "target_url": {
      +      "description": "Your HTTPS endpoint; `null` on every channel except `webhook`."
      +    },
      +    "test_url": {
      +      "description": "Returned on create only, when the channel delivers outside the dashboard: the path of `POST /v2/webhooks/{webhook}/test` for this record."
      +    },
      +    "ticker": {
      +      "description": "Event and news webhooks only: the symbols it is scoped to, or `null` for the universe or the whole market."
      +    },
      +    "universe": {
      +      "description": "Universe the trigger is scoped to, or `null` for the whole market."
      +    },
      +    "updated_at": {
      +      "description": "Last modification timestamp (epoch seconds).",
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "as_of",
      +    "id",
      +    "name",
      +    "q",
      +    "select",
      +    "order",
      +    "dir",
      +    "universe",
      +    "channel",
      +    "target_url",
      +    "status",
      +    "subscription_origin",
      +    "created_at",
      +    "updated_at",
      +    "last_fired",
      +    "channel_config",
      +    "signing_secret"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description does carry some weight: it discloses edge-triggered semantics ('starts matching', so no repeated alerts while the condition holds), the paid-plan gate, and a non-webhook fallback path. It omits other behavioral facts an agent creating a persistent subscription needs, such as whether duplicate subscriptions are rejected, what the create response returns, or that custom signals are frozen at creation (that detail lives only in the schema).

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?

Three short sentences, front-loaded with the trigger behavior and followed by the billing gate and the delivery fallback. Slightly muddled opening ('alert by webhook') for a tool that also supports discord, mobile push, and in-app delivery, but nothing is wasted.

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?

An output schema exists and the input schema is fully documented, so the description need not explain returns or parameters. It covers the trigger model, cost gating, and channel fallback, which are the non-obvious facts; only lifecycle details (duplicates, update/delete path) are unaddressed.

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

Parameters3/5

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

Schema description coverage is 100%, including enum-like `channel` and `cadence` value docs, so the schema already does the heavy lifting and the baseline is 3. The description's one parameter remark, omitting `target_url` for in-app delivery, duplicates what `channel`'s inference rule already states, adding no new meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: alert when one named ticker starts matching a condition, which is meaningfully narrower than the scan/event/news siblings. The single-ticker scope implicitly distinguishes it from subscribe_scan, but no sibling is named, so the agent must infer the boundary rather than read it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides two real usage constraints: webhooks require a paid plan (Free has no webhook slots) and omitting `target_url` yields in-app delivery. It never says when to pick this over subscribe_scan or subscribe_signal, even though `ticker IN (...)` alternatives are only mentioned inside the schema, so the when-to-use guidance is implied rather than stated.

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