Skip to main content
Glama
Tickerbot MCP Server

Tickerbot MCP Server

Official
by tickerbot

tickerbot_list_universes

Lists your custom ticker lists and the built-in universes (top_10, top_100), so you can pick the right universe slug to use with scan, signal and subscribe tools.

Instructions

Lists every universe you can use: your own ticker lists and the built-in ones. kind: builtin lists the built-in universes (top_10, top_100); omit it for yours; builtin,custom lists both. Use a slug as universe on scan, signal and subscribe tools.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tickerbot_list_universes"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoWhich universes to list: `builtin` (`top_10`, `top_100`), `custom` (your own) or both as a comma list. Leave it out for your own; from the cut-off on Deprecations it lists both. Values: builtin: A built-in universe, the same for every account: `top_10` and `top_100`. custom: One of your own universes.
limitNoPage size. Max 100.
cursorNoThe previous response's `next_cursor`. Send it with the same params as the first page (`limit` may change); a page whose params differ is a 400 naming the param.
searchNoOnly universes whose id, name or description contains this text (case-insensitive). Results are ranked across built-in and your own universes: an exact id or name match first, then an id or name that starts with the term, then one that contains it, then descriptions that have it as a whole word, then descriptions that contain it; list order within each rank. Paging a search never repeats or skips.

Output Schema

NameRequiredDescriptionDefault
as_ofYesServer time this response was assembled (ISO 8601); on an as-of read, the instant you asked for (As-of).
countYesThe universes in this page.
queryYesYour request echoed, each param with its effective value: `search` (`null` when not sent), `kind` (a list; the default when you left it out) and `limit`.
universesYesThe universes in scope, built-ins first, then yours newest first. Every result carries `kind` (`builtin` or `custom`).
_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).
next_cursorYesOpaque token for the next page; `null` on the last page. Pass it back as `cursor`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.4.1
    • changedInput schema / properties / cursor / description
      Previous value: -"Opaque cursor."New value: +"The previous response's `next_cursor`. Send it with the same params as the first page (`limit` may change); a page whose params differ is a 400 naming the param."
    • addedInput schema / properties / kind
      Added value: +{
      +  "description": "Which universes to list: `builtin` (`top_10`, `top_100`), `custom` (your own) or both as a comma list. Leave it out for your own; from the cut-off on Deprecations it lists both. Values: builtin: A built-in universe, the same for every account: `top_10` and `top_100`. custom: One of your own universes.",
      +  "pattern": "^\\s*([bB][uU][iI][lL][tT][iI][nN]|[cC][uU][sS][tT][oO][mM])(\\s*,\\s*([bB][uU][iI][lL][tT][iI][nN]|[cC][uU][sS][tT][oO][mM]))*\\s*$",
      +  "type": "string"
      +}
    • addedInput schema / properties / limit / default
      Added value: +50
    • changedInput schema / properties / limit / description
      Previous value: -"Page size (applies to your own; system universes are a small fixed set returned in full on the first page)."New value: +"Page size. Max 100."
    • removedInput schema / properties / owner
      Removed value: -{
      -  "description": "Which universes to list.",
      -  "enum": [
      -    "me",
      -    "system",
      -    "all"
      -  ],
      -  "type": "string"
      -}
    • addedInput schema / properties / search
      Added value: +{
      +  "description": "Only universes whose id, name or description contains this text (case-insensitive). Results are ranked across built-in and your own universes: an exact id or name match first, then an id or name that starts with the term, then one that contains it, then descriptions that have it as a whole word, then descriptions that contain it; list order within each rank. Paging a search never repeats or skips.",
      +  "type": "string"
      +}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "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"
      +      ]
      +    },
      +    "count": {
      +      "description": "The universes in this page.",
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "next_cursor": {
      +      "description": "Opaque token for the next page; `null` on the last page. Pass it back as `cursor`."
      +    },
      +    "query": {
      +      "description": "Your request echoed, each param with its effective value: `search` (`null` when not sent), `kind` (a list; the default when you left it out) and `limit`.",
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "universes": {
      +      "description": "The universes in scope, built-ins first, then yours newest first. Every result carries `kind` (`builtin` or `custom`).",
      +      "type": [
      +        "array",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "as_of",
      +    "query",
      +    "count",
      +    "next_cursor",
      +    "universes"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the behavioral burden; it discloses the default resolution for `kind` and notes the built-in set is account-independent. It never states that this is a read-only operation, says nothing about auth or rate limits, and leaves pagination behavior entirely to the schema.

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 tight sentences with the primary capability front-loaded, then the filtering modes, then the payoff of calling it. Nothing is padded and no sentence is wasted.

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 simple list tool with a full output schema and complete parameter documentation, the description covers what the tool returns conceptually and how the results are used. The remaining gap is the absence of any safety/read-only or auth framing, which matters little here but is 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 coverage is 100%, so all four parameters are documented, and the description's `kind` explanation largely restates the schema's own enumeration. The only genuine addition is the downstream note that a returned slug feeds `universe` on scan/signal/subscribe tools; `limit`, `cursor` and `search` get no treatment in the description.

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?

"Lists every universe you can use: your own ticker lists and the built-in ones" names a specific verb (lists) and resource (universes), and the built-in/custom distinction separates it from single-resource siblings like get_universe or create_universe.

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?

The description gives concrete operating context — omit `kind` for your own, `builtin` for top_10/top_100, `builtin,custom` for both — and points forward to where a returned slug is consumed (scan, signal and subscribe tools). It does not explicitly say when to prefer this over get_universe or create_universe, so it stops short of full alternative routing.

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