tickerbot_create_custom_signal
Save a named true/false SQL predicate to screen, select, and subscribe to custom signals like built-in booleans, referencing built-in and owned signals.
Instructions
Saves a named true/false SQL expression you can screen on, select and subscribe to like a built-in boolean.
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": {
"name": "<name>",
"expr": "<expr>"
},
"name": "tickerbot_create_custom_signal"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| expr | Yes | Boolean SQL predicate. May reference built-in signals and other custom signals you own. Must evaluate to true/false. Max 4000 chars. Stricter grammar than scan `q`: comparisons, `AND`/`OR`/`NOT`, `IN`, `BETWEEN`, `IS [NOT] NULL`, arithmetic and the functions `abs`/`coalesce`/`round`/`least`/`greatest`. An expression that scans fine can still be rejected here with `compile_failed`. What you send is what you read back: responses echo your expression as stored, not its expansion. A signal referencing another custom of yours returns the reference as you typed it; the inlined SQL exists only internally, and is what a subscribe endpoint freezes into a webhook. The one rewrite: a signal named under its pre-2026-09-07 spelling (`bollinger_pct_b`) is stored under its current name (`bollinger_b`) and reported in `_meta.deprecated_signals`. | |
| name | Yes | Slug matching `^[a-z][a-z0-9_]{0,63}$`. Must not collide with any built-in signal name, and 15 names are reserved outright: `columns`, plus the OHLCV aliases of the history read `open`/`high`/`low`/`close`/`volume`/`vwap`/`trades` and `o`/`h`/`l`/`c`/`v`/`vw`/`n` (those resolve to bars before custom lookup). This is the signal's API handle: it's what you reference in `q` and in the CRUD path. | |
| description | No | Free-form notes. Max 500 chars. Absent or empty comes back as `""` rather than null. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| expr | Yes | Your expression as stored (not its expansion). | |
| kind | Yes | Always `custom`. | |
| name | Yes | The slug: the signal's handle in `q` and in the path. | |
| type | Yes | Always `boolean`: a custom signal is a yes/no expression. | |
| _meta | No | Only when `expr` named a signal under its pre-2026-09-07 spelling: `deprecated_signals` lists each one (`requested`, `use`, `note`). The stored `expr` carries the current name. | |
| as_of | Yes | Server time this response was assembled (ISO 8601); on an as-of read, the instant you asked for (As-of). | |
| created_at | Yes | Creation timestamp (epoch seconds). | |
| updated_at | Yes | Last modification timestamp (epoch seconds). | |
| _advisories | No | 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). | |
| description | Yes | Your notes; `""` when unset. |