mcp-server

tickerbot_get_ticker

The full ticker row, every signal on the schema page, for one symbol or a comma list of up to 50. Right now, or with asof, as of any past date. Pass a comma list of up to 50 symbols for a batch (data keyed by symbol plus not_found). Crypto is the X-prefixed pair (X:BTCUSD) — bare BTC/ETH are US-listed ETFs.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`asof`	No	Optional. Target moment as `YYYY-MM-DD` (that day's close) or an ISO timestamp (that intraday moment) — the same read as it stood then, unlimited depth. Full contract under As of a past date.
`ticker`	Yes	One symbol, or a comma-separated list of up to 50 for a batch response keyed by symbol. Case-insensitive. Equities are bare symbols (`AAPL`); every other class carries a prefix — rates (`R:SOFR`), crypto (`X:BTCUSD`), fx (`X:EURUSD`). Bare `BTC`/`ETH` are US-listed ETFs, not spot crypto. See Tickers.
`interval`	No	Grain the past state is reconstructed at: `1m`, `1h`, `1d`, or `auto` (default). Only valid alongside `asof` — a live read with `interval` is a 400. Details under As of a past date.	auto

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	The full ticker row — every signal on the schema page. On the list form, an object keyed by symbol, one full row each.
`_meta`	No	With `asof` only: how the read was resolved — the interval served and requested, whether rows blend intervals, sources and frozen fields. See the as-of read below.
`as_of`	Yes	Server time this response was assembled (ISO 8601).
`count`	No	List form only — how many of `requested` were found.
`ticker`	No	The symbol you asked for, normalised. Single form only.
`not_found`	No	List form only — the requested symbols we do not track, in request order. An empty array when every symbol was found.
`requested`	No	List form only — the canonical symbols asked for, de-duplicated, in request order.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "_meta": {
+      "description": "With `asof` only: how the read was resolved — the interval served and requested, whether rows blend intervals, sources and frozen fields. See the as-of read below.",
+      "type": "object"
+    },
+    "as_of": {
+      "description": "Server time this response was assembled (ISO 8601).",
+      "type": "string"
+    },
+    "count": {
+      "description": "List form only — how many of `requested` were found.",
+      "type": "number"
+    },
+    "data": {
+      "description": "The full ticker row — every signal on the schema page. On the list form, an object keyed by symbol, one full row each.",
+      "type": "object"
+    },
+    "not_found": {
+      "description": "List form only — the requested symbols we do not track, in request order. An empty array when every symbol was found.",
+      "type": "string"
+    },
+    "requested": {
+      "description": "List form only — the canonical symbols asked for, de-duplicated, in request order.",
+      "type": "string"
+    },
+    "ticker": {
+      "description": "The symbol you asked for, normalised. Single form only.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "as_of",
+    "data"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedSep 17, 2026

changedInput schema / properties / asof / description

Previous value: -"Optional YYYY-MM-DD or ISO timestamp. Date-only returns the row at close of that day; a timestamp returns the row as of that moment (finest tier covering each column). Same meaning for one symbol or a list."New value: +"Optional. Target moment as `YYYY-MM-DD` (that day's close) or an ISO timestamp (that intraday moment) — the same read as it stood then, unlimited depth. Full contract under As of a past date."

addedInput schema / properties / interval

Added value: +{
+  "default": "auto",
+  "description": "Grain the past state is reconstructed at: `1m`, `1h`, `1d`, or `auto` (default). Only valid alongside `asof` — a live read with `interval` is a 400. Details under As of a past date.",
+  "enum": [
+    "1m",
+    "1h",
+    "1d",
+    "auto"
+  ],
+  "type": "string"
+}

changedInput schema / properties / ticker / description

Previous value: -"Symbol, or a comma-separated list of up to 50 (AAPL,MSFT,NVDA — a list answers `data` keyed by symbol). Case-insensitive. Equities: bare symbol (AAPL). Crypto: X-prefixed pair (X:BTCUSD) — bare BTC/ETH are US-listed ETFs, not spot crypto."New value: +"One symbol, or a comma-separated list of up to 50 for a batch response keyed by symbol. Case-insensitive. Equities are bare symbols (`AAPL`); every other class carries a prefix — rates (`R:SOFR`), crypto (`X:BTCUSD`), fx (`X:EURUSD`). Bare `BTC`/`ETH` are US-listed ETFs, not spot crypto. See Tickers."

Changed2 schema fields changedSep 8, 2026

changedInput schema / properties / asof / description

Previous value: -"Optional YYYY-MM-DD or ISO timestamp. Date-only returns the row at close of that day; a timestamp returns the row as of that moment (finest tier covering each column)."New value: +"Optional YYYY-MM-DD or ISO timestamp. Date-only returns the row at close of that day; a timestamp returns the row as of that moment (finest tier covering each column). Same meaning for one symbol or a list."

changedInput schema / properties / ticker / description

Previous value: -"Symbol. Case-insensitive. Equities: bare symbol (AAPL). Crypto: X-prefixed pair (X:BTCUSD) — bare BTC/ETH are US-listed ETFs, not spot crypto."New value: +"Symbol, or a comma-separated list of up to 50 (AAPL,MSFT,NVDA — a list answers `data` keyed by symbol). Case-insensitive. Equities: bare symbol (AAPL). Crypto: X-prefixed pair (X:BTCUSD) — bare BTC/ETH are US-listed ETFs, not spot crypto."

Changed2 schema fields changedJul 21, 2026

changedInput schema / properties / asof / description

Previous value: -"Optional YYYY-MM-DD. Returns the row at close of that day."New value: +"Optional YYYY-MM-DD or ISO timestamp. Date-only returns the row at close of that day; a timestamp returns the row as of that moment (finest tier covering each column)."

changedInput schema / properties / ticker / description

Previous value: -"Symbol. Case-insensitive. Equities: bare symbol (AAPL). Crypto: bare symbol (BTC)."New value: +"Symbol. Case-insensitive. Equities: bare symbol (AAPL). Crypto: X-prefixed pair (X:BTCUSD) — bare BTC/ETH are US-listed ETFs, not spot crypto."

First observedJun 11, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden and does it well: it explains live vs. asof reads, batch result keying, the not_found field, and the crypto prefix distinction. It does not discuss rate limits or failure modes, but it covers the most important behavioral traits.

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 dense sentences deliver the core behavior, batch capability, historical mode, and ticker-prefix caveat without filler. Key information is front-loaded.

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?

The tool is relatively complex, but the description covers the essential calling contexts: single vs. batch, live vs. asof, and the crypto/ETF distinction. With a full input schema and output schema present, the remaining parameter and return details are adequately covered.

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?

The input schema already documents all parameters at 100% coverage, including the asof format, interval constraints, and ticker naming conventions. The description adds a small amount of value by mentioning the batch response shape, but mostly restates what the schema already provides.

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 names a specific operation and resource: return the full ticker row with every signal for one symbol or a batch of up to 50. It is clear and specific, but it does not explicitly differentiate itself from sibling tools such as get_signal or get_bars.

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

Usage Guidelines3/5

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

The description implies when to use this tool, especially for getting the full current or historical ticker snapshot and for batch symbol lookups. However, it never explicitly contrasts this with alternatives or states when another sibling tool should be preferred.

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

All mcp-server tools Inspect

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.

tickerbot_get_ticker

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources