Skip to main content
Glama
Tickerbot MCP Server

Tickerbot MCP Server

Official
by tickerbot

tickerbot_update_universe

Update a universe's name, description, or tickers. Replace the full list or add and remove individual tickers; built-in universes stay read-only.

Instructions

Updates one of your universes: its name, description or members. tickers replaces the whole list; add/remove adjust it. Built-in universes cannot be edited.

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

Input Schema

NameRequiredDescriptionDefault
addNoAdd these tickers (deduplicated).
nameNoNew label. Non-empty, max 80 characters.
removeNoRemove these tickers.
tickersNoReplace the full ticker list (up to 10,000; validated against the tickers we track). Does not combine with `add`/`remove` (400).
universeYesUniverse slug.
descriptionNoNew notes. Max 500 characters.

Output Schema

NameRequiredDescriptionDefault
idYesThe slug: the universe's handle in `?universe=`.
kindYesAlways `custom` here: a universe you create or edit is yours. One of: `builtin`, `custom`.
nameYesDisplay label.
sizeYesMember count.
as_ofYesServer time this response was assembled (ISO 8601); on an as-of read, the instant you asked for (As-of).
tickersYesMembers, after this call.
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).
descriptionYesFree-form notes; `""` when unset.
effective_atNoBuilt-in universes only, in epoch seconds; absent on yours.
rebalance_methodNoBuilt-in universes only; absent on yours.
next_rebalance_atNoBuilt-in universes only, in epoch seconds; absent on yours.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.4.1
    • changedInput schema / properties / description / description
      Previous value: -"New notes."New value: +"New notes. Max 500 characters."
    • removedInput schema / properties / id
      Removed value: -{
      -  "description": "Universe slug.",
      -  "type": "string"
      -}
    • changedInput schema / properties / name / description
      Previous value: -"New label."New value: +"New label. Non-empty, max 80 characters."
    • changedInput schema / properties / tickers / description
      Previous value: -"Replace the full ticker list."New value: +"Replace the full ticker list (up to 10,000; validated against the tickers we track). Does not combine with `add`/`remove` (400)."
    • addedInput schema / properties / universe
      Added value: +{
      +  "description": "Universe slug.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "id"
      -]New value: +[
      +  "universe"
      +]
    • 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"
      +      ]
      +    },
      +    "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": "Free-form notes; `\"\"` when unset.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "effective_at": {
      +      "description": "Built-in universes only, in epoch seconds; absent on yours."
      +    },
      +    "id": {
      +      "description": "The slug: the universe's handle in `?universe=`.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "kind": {
      +      "description": "Always `custom` here: a universe you create or edit is yours. One of: `builtin`, `custom`.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "name": {
      +      "description": "Display label.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "next_rebalance_at": {
      +      "description": "Built-in universes only, in epoch seconds; absent on yours."
      +    },
      +    "rebalance_method": {
      +      "description": "Built-in universes only; absent on yours."
      +    },
      +    "size": {
      +      "description": "Member count.",
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "tickers": {
      +      "description": "Members, after this call.",
      +      "type": [
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "updated_at": {
      +      "description": "Last modification timestamp (epoch seconds).",
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "as_of",
      +    "id",
      +    "name",
      +    "description",
      +    "tickers",
      +    "size",
      +    "kind",
      +    "created_at",
      +    "updated_at"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose key behavior: full-list replacement semantics, incremental add/remove, mutual exclusivity, and the built-in-universe immutability guard. It omits permission requirements and whether removals are reversible, and never states the response shape (though an output schema exists).

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?

Three tight sentences, no filler. The core mutation semantics come first and the immutability caveat is placed as a final guard clause where an agent will see it before calling.

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?

With 100% schema coverage and an output schema, the definition only needs to add operational context, which it does via the replacement-vs-delta distinction and the built-in restriction. Only permission/auth expectations are left unstated.

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 the baseline is 3; the schema already documents 'tickers' vs 'add'/'remove' exclusivity and their 400 error. The description mostly restates that relationship rather than adding meaning such as dedup behavior, validation scope, or slug resolution.

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?

The description opens with a specific verb and resource ('Updates one of your universes') and enumerates the mutable facets (name, description, members), which cleanly separates it from the create/delete/get universe siblings. It stops just short of naming those 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete when-not constraint ('Built-in universes cannot be edited') and explains the two mutually exclusive editing modes ('tickers' replaces the whole list; 'add'/'remove' adjust it). It does not route the agent toward create/delete for universes that don't exist yet.

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