Skip to main content
Glama
Tickerbot MCP Server

Tickerbot MCP Server

Official
by tickerbot

tickerbot_create_universe

Creates a named ticker universe to scope screens and subscriptions, letting you save a reusable list of symbols for consistent filtering.

Instructions

Saves a named list of tickers to scope screens and subscriptions.

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": {
      "tickers": "<tickers>",
      "name": "<name>"
    },
    "name": "tickerbot_create_universe"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoOptional slug: the universe's permanent handle everywhere (`?universe=`, subscribe `universe`, CRUD path). Pattern `^[a-z][a-z0-9_]{0,62}$`: starts with a lowercase letter, then lowercase letters/digits/underscore, 63 chars max; the value is trimmed and lowercased before validation. `top_10` and `top_100` are reserved for built-in universes and rejected with 400. Must be unique within your account. Generated (`u_…`) if omitted.
nameYesDisplay name, up to 80 characters. Display only: the `id` is what references the universe.
tickersYesTicker symbols, up to 10,000. Validated against the tickers we track. `[]` is accepted: an empty universe you can fill later via PATCH.
descriptionNoFree-form notes, up to 500 characters. Stored as `""` when omitted.

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. Changed6 schema fields changedv0.4.1
    • changedInput schema / properties / description / description
      Previous value: -"Optional free-form notes."New value: +"Free-form notes, up to 500 characters. Stored as `\"\"` when omitted."
    • changedInput schema / properties / id / description
      Previous value: -"Optional slug (lowercase letters, digits, underscore). Auto-generated from name if omitted. Must be unique within the account."New value: +"Optional slug: the universe's permanent handle everywhere (`?universe=`, subscribe `universe`, CRUD path). Pattern `^[a-z][a-z0-9_]{0,62}$`: starts with a lowercase letter, then lowercase letters/digits/underscore, 63 chars max; the value is trimmed and lowercased before validation. `top_10` and `top_100` are reserved for built-in universes and rejected with 400. Must be unique within your account. Generated (`u_…`) if omitted."
    • changedInput schema / properties / name / description
      Previous value: -"Human-readable name."New value: +"Display name, up to 80 characters. Display only: the `id` is what references the universe."
    • changedInput schema / properties / tickers / description
      Previous value: -"List of ticker symbols."New value: +"Ticker symbols, up to 10,000. Validated against the tickers we track. `[]` is accepted: an empty universe you can fill later via PATCH."
    • changedInput schema / required
      Previous value: -[
      -  "name",
      -  "tickers"
      -]New value: +[
      +  "tickers",
      +  "name"
      +]
    • 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

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only conveys that this is a save/creation operation. It says nothing about uniqueness enforcement, reserved-id rejection, validation failures, or idempotency on repeat names — all behaviors an agent needs to predict before calling a mutation tool. The rich schema covers some of this, but the description itself adds almost no behavioral context.

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?

A single front-loaded sentence with the verb and resource first, and no filler. It is efficient but arguably too thin for a mutation endpoint, packing purpose and scope into one compact clause.

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?

For a four-parameter creation tool with no annotations, the output schema does relieve the description of explaining return values, and the input schema documents the fields thoroughly. Still missing is any note on mutation semantics — what happens when the name or id already exists — leaving the definition minimally viable rather than complete.

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 schema already explains id slug rules, name length, ticker limits, and the empty-array case. The description adds no parameter meaning beyond that, making the baseline 3 the correct score.

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 concrete verb and resource: 'Saves a named list of tickers,' which maps cleanly onto create-universe, and adds the downstream purpose ('to scope screens and subscriptions'). It never uses the word 'universe' nor distinguishes create from update/list/get/delete siblings, so an agent must rely on the tool name for differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The phrase 'to scope screens and subscriptions' hints at why a universe exists, but there is no explicit when-to-use guidance, no mention of the create-vs-update boundary (tickerbot_update_universe), and no prerequisites such as needing tickers that exist in the tracked set. Given five universe-related siblings, the missing routing is a real gap.

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