Skip to main content
Glama
Tickerbot MCP Server

Tickerbot MCP Server

Official
by tickerbot

tickerbot_get_ticker_coverage

Reports the data coverage and history range held for one ticker or up to 50 comma-separated symbols, so you can distinguish missing bars from absent coverage before diagnosing an outage.

Instructions

Reports what we hold for one ticker or a comma list of up to 50, and how far back, so an empty result is never ambiguous. Ask this before treating a gap in bars or history as an outage. An absent 1m span is not a gap: sub-hour bars load on the first request for a symbol.

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": {
      "ticker": "<ticker>"
    },
    "name": "tickerbot_get_ticker_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesOne symbol, or a comma-separated list of up to 50 for a response keyed by symbol. Case-insensitive. Equities are bare symbols (`NVDA`); 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.

Output Schema

NameRequiredDescriptionDefault
dataYesThe ticker's coverage (on the list form, an object keyed by symbol): `ticker` and `name`; `spans`, per grain (`bars`, `1d`, `1h`, `1m`), each `oldest`, `newest` and `rows`, with `bars` and `1d` adding `contiguous`, `expected_sessions`, `missing_sessions` and `gaps` (the sessions missing inside the span), `1h` and `1m` adding `measured_at`, and `1m` adding `included` and `rank` (whether the symbol is in the precomputed minute tier, which does not limit what bars you can read); `measured_signals`, the depth measured per signal where the backfill engine has probed (`signal`, `grain`, `first_date`, `last_date`, `pct_complete`); and `live_row`, the ticker's current state: `signals` (published signals it carries), `populated` and `null_signals` (those null on it right now; a symbol with no fundamentals, such as an OTC-traded ADR, lists them here).
as_ofYesServer time this response was assembled (ISO 8601); on an as-of read, the instant you asked for (As-of).
countNoWith a comma list only: the symbols in `data`, that is, how many of the symbols asked for were found.
queryYesYour request echoed: `ticker`, the symbols asked for (canonical, de-duplicated, in request order; a list even for one).
not_foundNoWith a comma list only: the requested symbols we do not track, in request order; an empty array when every symbol was found; every symbol when none was (still a 200).
_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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.1
    • changedInput schema / properties / ticker / description
      Previous value: -"Symbol."New value: +"One symbol, or a comma-separated list of up to 50 for a response keyed by symbol. Case-insensitive. Equities are bare symbols (`NVDA`); 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."
    • 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"
      +      ]
      +    },
      +    "count": {
      +      "description": "With a comma list only: the symbols in `data`, that is, how many of the symbols asked for were found."
      +    },
      +    "data": {
      +      "description": "The ticker's coverage (on the list form, an object keyed by symbol): `ticker` and `name`; `spans`, per grain (`bars`, `1d`, `1h`, `1m`), each `oldest`, `newest` and `rows`, with `bars` and `1d` adding `contiguous`, `expected_sessions`, `missing_sessions` and `gaps` (the sessions missing inside the span), `1h` and `1m` adding `measured_at`, and `1m` adding `included` and `rank` (whether the symbol is in the precomputed minute tier, which does not limit what bars you can read); `measured_signals`, the depth measured per signal where the backfill engine has probed (`signal`, `grain`, `first_date`, `last_date`, `pct_complete`); and `live_row`, the ticker's current state: `signals` (published signals it carries), `populated` and `null_signals` (those null on it right now; a symbol with no fundamentals, such as an OTC-traded ADR, lists them here).",
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "not_found": {
      +      "description": "With a comma list only: the requested symbols we do not track, in request order; an empty array when every symbol was found; every symbol when none was (still a 200)."
      +    },
      +    "query": {
      +      "description": "Your request echoed: `ticker`, the symbols asked for (canonical, de-duplicated, in request order; a list even for one).",
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "as_of",
      +    "query",
      +    "data"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the 50-symbol cap, that empty results are unambiguous, and the non-obvious behavior that absent sub-hour (`1m`) spans are not gaps because they load lazily on first request. It does not mention auth, rate limits, or response shape, but the output schema covers return values.

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?

Three sentences, front-loaded with what is reported, then the when-to-use trigger, then the lazy-load caveat. No filler; the final sentence is dense but earns its place by preventing a common misdiagnosis.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with an output schema, the description covers purpose, the diagnostic use case, the batch limit, and the one behavioral quirk (lazy sub-hour loading) that would otherwise cause false outage reports. Nothing needed to call it correctly is missing.

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 the rich per-parameter description already explains prefixes, case-insensitivity, and the BTC/ETH ETF trap. The description's mention of single-or-comma-list scope and the 50 cap largely restates the schema, so it adds little beyond baseline.

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: 'Reports what we hold for one ticker or a comma list of up to 50, and how far back' — that is clearly a data-coverage inspection tool. It differentiates itself from data-fetching siblings indirectly by framing the output as what is held and how far back, but it never names get_bars or get_history as the alternatives it complements.

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?

'Ask this before treating a gap in bars or history as an outage' gives a concrete triggering condition that tells the agent when to reach for this tool. It lacks an explicit when-not-to-use statement or named alternative, but the diagnostic framing is clear enough to route correctly.

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