Skip to main content
Glama
Tickerbot MCP Server

Tickerbot MCP Server

Official
by tickerbot

tickerbot_list_signals

Lists built-in and custom scan signals in one catalog, filterable by category, group, type, asset class and search, so you can find signal names and query terms before composing a scan.

Instructions

Lists every signal you can screen on: the built-ins and your custom signals, in one catalog you can filter, search and page. Use to discover the signal names and q vocabulary before composing a scan; custom signals appear with kind: custom. Narrow it with category, group, type, search and select=type,description rather than reading all ~460 rows.

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": "tickerbot_list_signals"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoFilter by kind (one or a comma list). Omit to return both. Values: builtin: A built-in signal, the same for every account. custom: One of your own custom signals.
typeNoOne value type or a comma list. Custom signals are always `boolean`. Values: numeric: Number. A price, ratio, count or score. boolean: Yes/no. Every custom signal is one. string: Text, such as a sector or an exchange. date: Date, `YYYY-MM-DD`. timestamp: Timestamp, an instant in ISO 8601. object: Object, a JSON object. string[]: List of text, such as the ETFs that hold a stock.
grainNoSignals with stored history at this grain (one or a comma list): what an as-of read or the history read can serve at it. Values: 1m: Minute. Signals with stored one-minute history. 1h: Hour. Signals with stored hourly history. 1d: Day. Signals with stored daily history.
groupNoOne taxonomy group or a comma list (`technicals,fundamentals`). Each signal carries its `group`. Values: price: Price. Price levels and records: the current price, bars, session levels, rolling highs and lows, and support and resistance. volume: Volume. How much traded: absolute quantities and averages, and activity relative to baseline. price_action: Price action. How price is moving, read straight off the price record: changes, gaps, momentum episodes, range structures. technicals: Technicals. Named technical indicators (SMA, EMA, VWAP, RSI, MACD, ADX, Bollinger, ATR) and the signals built on them. fundamentals: Fundamentals. Company financials: statement lines as reported, the ratios and multiples built on them, share structure and short positioning. events: Events. What happened or is scheduled to happen to the company: earnings, dividends, IPOs, share-capital changes, insider transactions. profile: Profile. Who and what the security is: classification and identity data, looked up rather than computed. analyst: Analysts. What analysts think: the consensus, each firm’s actions, price targets and estimates. news: News. Signals derived from news coverage: article volume and sentiment.
limitNoPage size over the whole list: your custom signals (newest first), then the built-ins A→Z. Max 500 until 2027-01-12, then 100 (a larger value is clamped to the max, not an error; `next_cursor` pages the rest; see Deprecations). Omitted, every matching signal comes back in one response until 2027-01-12; after that a call pages at a default limit.
cursorNoThe previous response's `next_cursor`. Send it with the same params as the first page (`limit` may change); a page whose params differ is a 400 naming the param.
searchNoCase-insensitive text match on the name and description. Results are ranked: an exact name match first, then names that start with the term, then names that contain it, then descriptions that have it as a whole word, then descriptions that contain it; list order within each rank. Paging a search never repeats or skips.
selectNoThe fields each row carries (`name` is always included), e.g. `type,description`.
refreshNoSignals that update on this schedule (one or a comma list). Values: 1m_4am_8pm_et: 1 min · 4 AM–8 PM ET. 1m_24_7: 1 min · 24/7. 5m: 5 min. 10m: 10 min. 15m: 15 min. 30m: 30 min. 1h: hourly. daily: daily. daily_after_close: post-close daily. weekly: weekly. monthly: monthly. quarterly: quarterly. on_event: on event. static: static. custom: custom.
categoryNoOne category or a comma list (`oscillators,trend`). Each signal carries its `category`. Values: trades_quotes: Trades & quotes. bars: Latest bars. session_structure: Session levels & position. highs_lows: Highs & lows. support_resistance: Support & resistance. volume_levels: Volume & averages. volume_activity: Relative & unusual volume. performance: Performance & change. gaps: Gaps. intraday_momentum: Intraday momentum. ranges: Ranges & reversals. moving_averages: Moving averages & VWAP. oscillators: Oscillators. trend: Trend & direction. volatility_bands: Volatility & bands. income_statement: Income statement. balance_sheet: Balance sheet. cash_flow: Cash flow. margins_ratios: Margins & ratios. valuation: Valuation. share_structure: Share structure & ownership. short_interest: Short interest. earnings: Earnings. dividends: Dividends. ipos: IPOs. capital_changes: Splits & share changes. insider_activity: Insider activity. classification: Classification. identity: Identifiers & reference. company: Company profile. fund_facts: Fund facts. consensus_ratings: Consensus ratings. analyst_actions: Upgrades & downgrades. price_targets: Price targets. estimates: Estimates. news: News.
asset_classNoSignals that apply to this asset class (one or a comma list), e.g. `crypto`. Values: stocks: US equities. All US-listed equities (NYSE, Nasdaq, AMEX) rates: Rates. NY Fed reference rates + the Treasury par yield curve, under the R: prefix. crypto: Crypto. Crypto pairs under the X: prefix in `ticker`. fx: FX. Curated major currency pairs under the X: prefix.

Output Schema

NameRequiredDescriptionDefault
as_ofYesServer time this response was assembled (ISO 8601); on an as-of read, the instant you asked for (As-of).
countYesSignals in this page, equal to `count_builtin` + `count_custom`.
queryYesYour request echoed, each param with its effective value: `search`, then `kind`, `group`, `category`, `type`, `asset_class`, `refresh` and `grain` (lists), `select` and `limit` (`null` on a call with no `limit`, which returns the whole list). A filter you did not send is `null`.
signalsYesThe catalog: your custom signals first, then built-ins. Each built-in carries `name`, `kind: builtin`, `type`, `description`, `category`/`category_label`/`group`/`group_label` (switch on the slugs; labels are display strings), `refresh` (how often it updates), `grains` (keyed by stored grain, each `{ history, since, coverage }`; `{}` means current value only), `asset_classes`, `instrument_scope` (`all`, `company` or `fund`), `asof_support` (`historized`, `frozen` or `unavailable`: what an `asof` read does with it), plus `boolean_kind`/`firing` on yes/no signals, `definition` where written and `unit` where one applies. Custom signals are always yes/no: `kind: custom`, `type: boolean`, with the `expr`.
_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).
next_cursorYesOpaque token for the next page; `null` on the last page. Pass it back as `cursor`.
count_customYesYour custom signals in this page.
count_builtinYesBuilt-in signals in this page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.1

TDQS

A4.2/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 well: it discloses catalog scale (~460 rows), that custom signals are tagged `kind: custom`, and that a full unfiltered read is expensive. It does not restate safety or mutability, but this is a read-only list tool where that matters less than the volume warning it does provide.

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?

Two sentences, front-loaded with what the tool returns, then when to use it, then how to narrow it. No filler, no restatement of the title, and the scale warning is placed where it drives the filtering advice.

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 an 11-parameter catalog tool with an output schema, the description covers identity, scale, and the recommended narrowing strategy, while pagination and cursor semantics are fully documented in the schema. Only a note on ordering or default page behavior is missing, which the schema already supplies.

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 coverage is 100% and every filter's enum values and semantics are already spelled out in the schema, so the schema does the heavy lifting. The description names the useful narrowers (`category`, `group`, `type`, `search`, `select=type,description`) and gives a concrete select example, but adds little beyond what the parameter docs already contain.

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 and resource ('Lists every signal you can screen on'), names both populations covered (built-ins plus custom signals), and frames the output as a single filterable catalog. An agent can immediately distinguish this from get_signal or scan without opening any 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?

Explicitly says when to reach for it: 'Use to discover the signal names and `q` vocabulary before composing a scan.' That is a concrete prerequisite role rather than a vague hint. It stops short of naming the scan tool or stating a when-not condition, so it is not a full 5.

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