Skip to main content
Glama
Tickerbot MCP Server

Tickerbot MCP Server

Official
by tickerbot

tickerbot_delete_universe

Permanently delete a universe; when webhooks reference it and deletion returns 409, set force=true to delete it and disable those webhooks at their next evaluation.

Instructions

Permanently deletes one of your universes. A universe any of your webhooks still uses answers 409 universe_referenced; force=true deletes it, and those webhooks are disabled at their next evaluation.

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": {
      "universe": "<universe>"
    },
    "name": "tickerbot_delete_universe"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoA universe that any of your webhooks references (active or disabled) refuses to delete with `409 universe_referenced`, listing them in `referencing_webhooks`. Pass `force=true` to delete anyway; those webhooks are disabled at their next evaluation.
universeYesUniverse slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.4.1
    • addedInput schema / properties / force
      Added value: +{
      +  "default": false,
      +  "description": "A universe that any of your webhooks references (active or disabled) refuses to delete with `409 universe_referenced`, listing them in `referencing_webhooks`. Pass `force=true` to delete anyway; those webhooks are disabled at their next evaluation.",
      +  "type": "boolean"
      +}
    • removedInput schema / properties / id
      Removed value: -{
      -  "description": "Universe slug.",
      -  "type": "string"
      -}
    • addedInput schema / properties / universe
      Added value: +{
      +  "description": "Universe slug.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "id"
      -]New value: +[
      +  "universe"
      +]
  2. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does well: it discloses that the operation is permanent, that it returns 409 universe_referenced with a referencing_webhooks list, and that force=true disables those webhooks at their next evaluation. What it omits is whether deletion cascades to other dependent resources (custom signals, subscriptions) and whether any confirmation or elevated permission is required.

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 with zero filler. The destructive outcome is front-loaded, and the conditional/force behavior follows in the order an agent would encounter it during a call.

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 essential risk surface: permanence, the conflict response, and the force side effect. The remaining gap is the absence of cascade information about other resources bound to the universe.

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%, so both parameters are fully documented in the schema, giving a baseline of 3. The description restates the force parameter's conflict behavior almost verbatim rather than adding new semantics such as slug formatting or case sensitivity, so it does not exceed the baseline.

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?

The description opens with a specific verb and resource: 'Permanently deletes one of your universes.' The word 'permanently' distinguishes it from tickerbot_update_universe, and the 'universe' scoping separates it from tickerbot_delete_webhook and tickerbot_delete_custom_signal, so an agent can route to it without inspecting schemas.

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 context is implied by naming the resource and the destructive outcome, and the 409 path tells the agent when a retry with force is warranted. However, there is no explicit guidance on prerequisites (e.g., listing universes first to obtain a slug) or on alternatives such as updating instead of deleting, so the agent must infer those.

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