Skip to main content
Glama

mcp-server

by io.github.tickerbot
OverviewDiscussionsAdmin

tickerbot_list_tickers

Every symbol we track, active or delisted, as one identity row each. Use /v2/tickers/{ticker} for the full row.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoPage size. Max 1000.
cursorNoOpaque cursor from the previous response's `next_cursor` field. Continues the walk from after that page. A cursor minted under `search` only resumes the same search.
searchNoCase-insensitive match on `ticker` or `name`, max 64 characters (longer is a 400). Results are ranked: an exact ticker match first, then symbols that start with the term, then name matches — alphabetical within each rank. The cursor carries the rank, so paging a search never repeats or skips.
exchangeNoFilter by exchange name — the value rows carry in their `exchange` field. MIC codes (`XNAS`, `XNYS`, `BATS`) are also accepted and match `exchange_mic`. A malformed value (non-letters, over 16 chars) is a 400.
asset_typeNoFilter by instrument type WITHIN equities — the stored `asset_type` value (`CS`, `ETF`, `ADRC`, `PFD`, `FUND`, `UNIT`, `SP`, `ETS`, `WARRANT`, `RIGHT`, `ETN`, `ETV`), matched case-insensitively. `equity` is a convenience value expanding to the equity-like set. This is NOT an asset class: `asset_type=crypto` is rejected — use `asset_class=crypto`.
asset_classNoFilter by asset class — `stocks`, `rates`, `crypto`, `fx`, or a comma-separated list (the live classes today; validated for shape, not against a fixed list, so a well-formed class we don't track simply matches nothing — same contract as scan). Omit for every class. This is the class of INSTRUMENT, distinct from `asset_type` below (the instrument type within equities). Every row carries its `asset_class`, so a non-equity row identifies itself.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
as_ofYesServer time this response was assembled (ISO 8601).
countYesRows in this page.
resultsYesOne identity row per symbol — the thirteen signals named above, nothing else. `active: false` rows carry `delisted_utc`; they are still addressable on the state route with `asof`.
next_cursorYesOpaque token for the next page; `null` on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "as_of": {
+      "description": "Server time this response was assembled (ISO 8601).",
+      "type": "string"
+    },
+    "count": {
+      "description": "Rows in this page.",
+      "type": "number"
+    },
+    "next_cursor": {
+      "description": "Opaque token for the next page; `null` on the last page.",
+      "type": "string"
+    },
+    "results": {
+      "description": "One identity row per symbol — the thirteen signals named above, nothing else. `active: false` rows carry `delisted_utc`; they are still addressable on the state route with `asof`.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "as_of",
+    "count",
+    "next_cursor",
+    "results"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • removedInput schema / properties / exchange / enum
      Removed value: -[
-  "NASDAQ",
-  "NYSE",
-  "NYSE Arca",
-  "Cboe BZX",
-  "NYSE American",
-  "OTC Link"
-]
  3. Changed9 schema fields changed
    • changedInput schema / properties / asset_class / description
      Previous value: -"Filter by asset class — `stocks`, `rates`, `crypto`, `fx`, or a comma-separated list. Omit for every class. Distinct from asset_type (the instrument type within equities)."New value: +"Filter by asset class — `stocks`, `rates`, `crypto`, `fx`, or a comma-separated list (the live classes today; validated for shape, not against a fixed list, so a well-formed class we don't track simply matches nothing — same contract as scan). Omit for every class. This is the class of INSTRUMENT, distinct from `asset_type` below (the instrument type within equities). Every row carries its `asset_class`, so a non-equity row identifies itself."
    • changedInput schema / properties / asset_type / description
      Previous value: -"Filter by INSTRUMENT TYPE within equities: the stored value (CS, ETF, ADRC, PFD, FUND, UNIT, SP, ETS, WARRANT, RIGHT, ETN, ETV), or \"equity\" for the equity-like set. This is not an asset class — `asset_type=crypto` is rejected; use asset_class=crypto."New value: +"Filter by instrument type WITHIN equities — the stored `asset_type` value (`CS`, `ETF`, `ADRC`, `PFD`, `FUND`, `UNIT`, `SP`, `ETS`, `WARRANT`, `RIGHT`, `ETN`, `ETV`), matched case-insensitively. `equity` is a convenience value expanding to the equity-like set. This is NOT an asset class: `asset_type=crypto` is rejected — use `asset_class=crypto`."
    • addedInput schema / properties / asset_type / enum
      Added value: +[
+  "CS",
+  "ETF",
+  "ADRC",
+  "PFD",
+  "FUND",
+  "UNIT",
+  "SP",
+  "ETS",
+  "WARRANT",
+  "RIGHT",
+  "ETN",
+  "ETV",
+  "equity"
+]
    • changedInput schema / properties / cursor / description
      Previous value: -"Opaque cursor from a prior response."New value: +"Opaque cursor from the previous response's `next_cursor` field. Continues the walk from after that page. A cursor minted under `search` only resumes the same search."
    • changedInput schema / properties / exchange / description
      Previous value: -"Filter by exchange name (NASDAQ, NYSE, NYSE Arca, Cboe BZX, NYSE American, OTC Link) or MIC (XNAS, XNYS, BATS)."New value: +"Filter by exchange name — the value rows carry in their `exchange` field. MIC codes (`XNAS`, `XNYS`, `BATS`) are also accepted and match `exchange_mic`. A malformed value (non-letters, over 16 chars) is a 400."
    • addedInput schema / properties / exchange / enum
      Added value: +[
+  "NASDAQ",
+  "NYSE",
+  "NYSE Arca",
+  "Cboe BZX",
+  "NYSE American",
+  "OTC Link"
+]
    • addedInput schema / properties / limit / default
      Added value: +50
    • changedInput schema / properties / limit / description
      Previous value: -"Page size. Max 1000. Default 50."New value: +"Page size. Max 1000."
    • changedInput schema / properties / search / description
      Previous value: -"Case-insensitive match on ticker or name (max 64 chars). Ranked: exact ticker, then ticker prefix, then name match, alphabetical within."New value: +"Case-insensitive match on `ticker` or `name`, max 64 characters (longer is a 400). Results are ranked: an exact ticker match first, then symbols that start with the term, then name matches — alphabetical within each rank. The cursor carries the rank, so paging a search never repeats or skips."
  4. Changed7 schema fields changed
    • changedInput schema / properties / asset_type / description
      Previous value: -"Filter by INSTRUMENT TYPE within equities: the stored value (CS, ETF, ADRC, PFD, FUND, UNIT, SP, ETS, WARRANT, RIGHT, ETN, ETV), or \"equity\" for the equity-like set. This is not an asset class — `asset_type=crypto` is rejected; crypto is in the main list under its X: symbols."New value: +"Filter by INSTRUMENT TYPE within equities: the stored value (CS, ETF, ADRC, PFD, FUND, UNIT, SP, ETS, WARRANT, RIGHT, ETN, ETV), or \"equity\" for the equity-like set. This is not an asset class — `asset_type=crypto` is rejected; use asset_class=crypto."
    • changedInput schema / properties / exchange / description
      Previous value: -"Filter by exchange (e.g. \"XNYS\", \"XNAS\", \"BATS\")."New value: +"Filter by exchange name (NASDAQ, NYSE, NYSE Arca, Cboe BZX, NYSE American, OTC Link) or MIC (XNAS, XNYS, BATS)."
    • removedInput schema / properties / min_market_cap
      Removed value: -{
-  "description": "Minimum market cap in USD. Orders results by market_cap desc.",
-  "type": "number"
-}
    • changedInput schema / properties / search / description
      Previous value: -"Case-insensitive substring filter on ticker/name. Orders results by market_cap desc."New value: +"Case-insensitive match on ticker or name (max 64 chars). Ranked: exact ticker, then ticker prefix, then name match, alphabetical within."
    • removedInput schema / properties / sector
      Removed value: -{
-  "description": "Exact-match sector filter (e.g. \"Technology\").",
-  "type": "string"
-}
    • removedInput schema / properties / tickers
      Removed value: -{
-  "description": "Comma-separated symbols (max 50). When set, returns full rows for these symbols and pagination params are ignored.",
-  "type": "string"
-}
    • removedInput schema / properties / universe
      Removed value: -{
-  "description": "Restrict to a universe slug (top_10, top_100, or a saved one).",
-  "type": "string"
-}
  5. Changed2 schema fields changed
    • addedInput schema / properties / asset_class
      Added value: +{
+  "description": "Filter by asset class — `stocks`, `rates`, `crypto`, `fx`, or a comma-separated list. Omit for every class. Distinct from asset_type (the instrument type within equities).",
+  "type": "string"
+}
    • addedInput schema / properties / universe
      Added value: +{
+  "description": "Restrict to a universe slug (top_10, top_100, or a saved one).",
+  "type": "string"
+}
  6. Changed1 schema field changed
    • changedInput schema / properties / asset_type / description
      Previous value: -"Filter by asset type (e.g. \"equity\", \"crypto\")."New value: +"Filter by INSTRUMENT TYPE within equities: the stored value (CS, ETF, ADRC, PFD, FUND, UNIT, SP, ETS, WARRANT, RIGHT, ETN, ETV), or \"equity\" for the equity-like set. This is not an asset class — `asset_type=crypto` is rejected; crypto is in the main list under its X: symbols."
  7. First observed

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It usefully reveals that delisted symbols are included and that rows are identity-only rather than full records. However, it does not mention default page size, pagination, or the read-only nature of the call; the schema covers some of this, but the description itself is minimally transparent.

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?

The description is two short sentences with no redundancy. The core behavior is front-loaded, and the pointer to the full-row endpoint earns its place as a disambiguator.

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?

Given that an output schema exists and the input schema documents all six optional parameters, the description does not need to restate return values or parameter details. It supplies the missing context: identity-row semantics, delisted coverage, and where to get full data. It is slightly incomplete only in not contrasting this tool with other list/scan siblings.

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 description adds no parameter-level meaning beyond what the schema already provides. It neither clarifies parameter behavior nor introduces constraints, so it does not deserve a higher score.

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 states the resource (every symbol tracked), the scope (active or delisted), and the granularity (one identity row each), which is specific and informative. It also distinguishes this list operation from the full-row retrieval via `/v2/tickers/{ticker}`, matching the sibling `get_ticker` tool.

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 implies when to use the list: when you want identity rows for tracked symbols, active or delisted. It explicitly points to `/v2/tickers/{ticker}` for the full row, giving a clear alternative for a different need. It does not enumerate other alternatives like `scan` or `get_ticker_coverage`, so it falls just short of full routing guidance.

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

All mcp-server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources