Skip to main content
Glama
Tickerbot MCP Server

Tickerbot MCP Server

Official
by tickerbot

tickerbot_get_universe

Retrieve a single stock or crypto universe by slug, including built-in top_10 and top_100 lists or one you own.

Instructions

Returns one universe: a built-in (top_10, top_100) or one you own.

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

Input Schema

NameRequiredDescriptionDefault
universeYesUniverse slug: a built-in (`top_10`, `top_100`) or one of yours.

Output Schema

NameRequiredDescriptionDefault
idYesThe slug: the universe's handle in `?universe=`.
kindYesWhose universe it is. 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.
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: when this membership took effect (epoch seconds).
rebalance_methodNoBuilt-in universes only: how membership is chosen.
next_rebalance_atNoBuilt-in universes only: when membership is next recomputed (epoch seconds).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.4.1
    • removedInput schema / properties / id
      Removed value: -{
      -  "description": "Universe slug.",
      -  "type": "string"
      -}
    • addedInput schema / properties / universe
      Added value: +{
      +  "description": "Universe slug: a built-in (`top_10`, `top_100`) or one of yours.",
      +  "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: when this membership took effect (epoch seconds).",
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "id": {
      +      "description": "The slug: the universe's handle in `?universe=`.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "kind": {
      +      "description": "Whose universe it is. One of: `builtin`, `custom`.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "name": {
      +      "description": "Display label.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "next_rebalance_at": {
      +      "description": "Built-in universes only: when membership is next recomputed (epoch seconds).",
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "rebalance_method": {
      +      "description": "Built-in universes only: how membership is chosen.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "size": {
      +      "description": "Member count.",
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "tickers": {
      +      "description": "Members.",
      +      "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

B3.2/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 full behavioral burden. 'Returns' implies a non-mutating read and the enumeration of built-in slugs adds useful context, but it says nothing about error behavior for an unknown or non-owned slug, nor whether authentication is required to resolve 'one you own'. An output schema exists, so return-value detail is not owed.

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 no waste. Its brevity borders on under-specification rather than over-verbosity, which is the right failure mode for a one-parameter lookup.

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?

The tool is simple, the single parameter is fully documented, and an output schema covers the response shape, so most needs are met. What is missing is guidance on invalid-slug behavior and any pointer distinguishing this from the sibling universe-listing and universe-creation tools.

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% and the parameter description already names the slug format and built-ins. The description restates the same information without adding syntax, case sensitivity, or validation rules, so the schema does the real work and 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 ('Returns one universe') and enumerates the built-in slugs, so an agent knows exactly what this fetches. It does not explicitly distinguish itself from the sibling tickerbot_list_universes, which is the main ambiguity an agent faces here.

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 description provides no when-to-use guidance and no exclusions. It never says to use tickerbot_list_universes to enumerate options first or to use tickerbot_create_universe for universes that don't yet exist, so the agent must infer routing from names alone.

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