Skip to main content
Glama
Tickerbot MCP Server

Tickerbot MCP Server

Official
by tickerbot

tickerbot_delete_custom_signal

Deletes a custom signal by slug, refusing if another signal references it; use force to skip the reference check and delete anyway.

Instructions

Deletes one of your custom signals. Refused by default if another of your signals references it.

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_delete_custom_signal"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoWhen `true`, skip the reference check and delete; referencing signals fail with `unknown_column` the next time they compile.
signalYesCustom signal slug (the signal name). A built-in name answers 404: built-ins are read-only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.4.1
    • addedInput schema / properties / force / default
      Added value: +false
    • changedInput schema / properties / force / description
      Previous value: -"When true, skip the reference check and delete anyway. Default false."New value: +"When `true`, skip the reference check and delete; referencing signals fail with `unknown_column` the next time they compile."
    • removedInput schema / properties / name
      Removed value: -{
      -  "description": "Custom signal slug.",
      -  "type": "string"
      -}
    • 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"
      +]
  2. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the default refusal when another signal references the target and the downstream consequence of forcing (referencing signals fail with `unknown_column` at next compile). It does not state irreversibility or permission requirements, which keeps it from a 5.

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, zero waste, with the destructive action front-loaded and the default guardrail immediately after. Nothing is repeated from the schema verbatim.

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 a two-parameter destructive tool with no annotations and no output schema, the description covers the action, the safety default, and the consequence of bypassing it. Only irreversibility/permission context is missing, which is a modest gap rather than a blocking one.

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 both parameters are fully documented in the schema, including the `force` default and its failure mode. The description's reference-check sentence reinforces the meaning of `force` but adds no syntax or format detail beyond the schema, so 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: 'Deletes one of your custom signals.' The resource scoping ('custom signals', not universes or webhooks) distinguishes it from the other delete_* siblings without naming them. It stops short of an explicit sibling callout, so a 4 rather than a 5.

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 implied by the resource name and the guardrail sentence, but there is no explicit 'use this when you want to remove a signal you no longer need' or a pointer to update_custom_signal as the non-destructive alternative. The refusal condition is stated, which is useful, but it is a behavioral constraint rather than when-to-use routing.

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