Skip to main content
Glama
Tickerbot MCP Server

Tickerbot MCP Server

Official
by tickerbot

tickerbot_update_custom_signal

Update a custom signal you own by changing its SQL expression, description, or name; validation keeps references consistent.

Instructions

Updates a custom signal you own: its expression, description or name.

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": {
      "signal": "<signal>"
    },
    "name": "tickerbot_update_custom_signal"
  }
}

Input Schema

NameRequiredDescriptionDefault
exprNoNew SQL expression. Re-validated and re-inlined against your other custom signals. Same strict grammar as create: no `LIKE`/`ILIKE`, `CASE`, `::` casts or functions beyond `abs`/`coalesce`/`round`/`least`/`greatest`. The response echoes your expression as stored, not its expansion (a pre-2026-09-07 signal spelling is stored under its current name and reported in `_meta.deprecated_signals`).
signalYesCustom signal slug (the signal name). A built-in name answers 404: built-ins are read-only.
new_nameNoNew slug: renames the signal and changes its API handle everywhere (same validation as create). Refused while other custom signals reference the current name.
descriptionNoNew description. Not derived from `expr`, so change both if the prose describes a threshold you are moving.

Output Schema

NameRequiredDescriptionDefault
exprYesYour expression as stored (not its expansion).
kindYesAlways `custom`.
nameYesThe slug: the signal's handle in `q` and in the path.
typeYesAlways `boolean`: a custom signal is a yes/no expression.
_metaNoOnly 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_ofYesServer time this response was assembled (ISO 8601); on an as-of read, the instant you asked for (As-of).
created_atYesCreation timestamp (epoch seconds).
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).
descriptionYesYour notes; `""` when unset.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.4.1
    • changedInput schema / properties / description / description
      Previous value: -"New description."New value: +"New description. Not derived from `expr`, so change both if the prose describes a threshold you are moving."
    • changedInput schema / properties / expr / description
      Previous value: -"New SQL WHERE expression. Re-validated on save."New value: +"New SQL expression. Re-validated and re-inlined against your other custom signals. Same strict grammar as create: no `LIKE`/`ILIKE`, `CASE`, `::` casts or functions beyond `abs`/`coalesce`/`round`/`least`/`greatest`. The response echoes your expression as stored, not its expansion (a pre-2026-09-07 signal spelling is stored under its current name and reported in `_meta.deprecated_signals`)."
    • removedInput schema / properties / name
      Removed value: -{
      -  "description": "CURRENT slug — identifies which signal to edit.",
      -  "type": "string"
      -}
    • changedInput schema / properties / new_name / description
      Previous value: -"Rename the signal to this slug (snake_case, must not collide with a built-in column or another of your signals)."New value: +"New slug: renames the signal and changes its API handle everywhere (same validation as create). Refused while other custom signals reference the current name."
    • addedInput schema / properties / signal
      Added value: +{
      +  "description": "Custom signal slug (the signal name). A built-in name answers 404: built-ins are read-only.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "name"
      -]New value: +[
      +  "signal"
      +]
    • 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": "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": {
      +      "description": "Server time this response was assembled (ISO 8601); on an as-of read, the instant you asked for (As-of).",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "created_at": {
      +      "description": "Creation timestamp (epoch seconds).",
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "description": {
      +      "description": "Your notes; `\"\"` when unset.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "expr": {
      +      "description": "Your expression as stored (not its expansion).",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "kind": {
      +      "description": "Always `custom`.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "name": {
      +      "description": "The slug: the signal's handle in `q` and in the path.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "type": {
      +      "description": "Always `boolean`: a custom signal is a yes/no expression.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "updated_at": {
      +      "description": "Last modification timestamp (epoch seconds).",
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "as_of",
      +    "name",
      +    "kind",
      +    "type",
      +    "description",
      +    "expr",
      +    "created_at",
      +    "updated_at"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.2.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: no mention of re-validation on write, the rename-in-use refusal, or the partial-update semantics (are omitted fields left untouched?). The mutation's failure modes and side effects only surface in the parameter schema text, not the description.

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?

One sentence, front-loaded with the verb, resource, and mutable field set, with zero filler. It is arguably under-sized for a mutation with rename side effects, but nothing written is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need no explanation, and the parameters are fully documented. What remains missing at the description level is the mutation contract itself: partial vs full update, the validate-then-apply failure behavior, and rename consequences, which for an unannotated write tool is a real gap.

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%, with each of the four parameters documented in depth (grammar restrictions, rename refusal, deprecation echo). The description adds only the field list mapped above and no syntax or format detail beyond the schema, so the baseline 3 applies.

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 ("Updates a custom signal you own") and enumerates the three mutable fields, so an agent can tell it apart from create/delete siblings without opening the schema. It stops short of naming the sibling alternatives explicitly.

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?

Usage is only implied: "a custom signal you own" signals that the target must be an existing, user-owned signal, and the schema adds that built-ins return 404. There is no explicit statement of when to use this versus create_custom_signal or how to discover the slug first.

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