mcp-server

tickerbot_get_ticker_coverage

For one ticker, what we hold and how far back — so an empty result is never ambiguous. Ask this before treating a gap in bars or series as an outage. minute_tier.included: false with on_demand: true is not a gap — sub-hour bars fetch from the provider on first request.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ticker`	Yes	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.

Output Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Company or instrument name.
`as_of`	Yes	Server time this response was assembled (ISO 8601).
`spans`	Yes	Per resolution — `oldest`, `newest`, `rows`.
`ticker`	Yes	The symbol you asked for.
`minute_tier`	Yes	Whether this ticker is in the minute tier (`included`) and its `rank` within it. `included:false` is NOT "no intraday data": the object then carries `on_demand: true`, `first_call_latency` (`"3-10s"`) and `window_days` (31) — sub-hour bars for the symbol are fetched from the provider on first request and stored, so the first call is slow and later ones are sub-second.
`measured_fields`	Yes	Per-field measured depth where the backfill engine has probed — `field`, the grain it was measured at (`daily`, `hourly`, `minute`), `first_date`, `last_date`, `pct_complete`. Capped at 1500 rows.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "as_of": {
+      "description": "Server time this response was assembled (ISO 8601).",
+      "type": "string"
+    },
+    "measured_fields": {
+      "description": "Per-field measured depth where the backfill engine has probed — `field`, the grain it was measured at (`daily`, `hourly`, `minute`), `first_date`, `last_date`, `pct_complete`. Capped at 1500 rows.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "minute_tier": {
+      "description": "Whether this ticker is in the minute tier (`included`) and its `rank` within it. `included:false` is NOT \"no intraday data\": the object then carries `on_demand: true`, `first_call_latency` (`\"3-10s\"`) and `window_days` (31) — sub-hour bars for the symbol are fetched from the provider on first request and stored, so the first call is slow and later ones are sub-second.",
+      "type": "object"
+    },
+    "name": {
+      "description": "Company or instrument name.",
+      "type": "string"
+    },
+    "spans": {
+      "description": "Per resolution — `oldest`, `newest`, `rows`.",
+      "type": "object"
+    },
+    "ticker": {
+      "description": "The symbol you asked for.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "as_of",
+    "ticker",
+    "name",
+    "minute_tier",
+    "spans",
+    "measured_fields"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 17, 2026

changedInput schema / properties / ticker / description

Previous value: -"Symbol."New value: +"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."

AddedAug 7, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With no annotations, the description carries the full burden, and it delivers: it explains that an empty result is meaningful, not ambiguous, and that `minute_tier.included: false` with `on_demand: true` is expected behavior because sub-hour bars fetch on first request. This prevents a caller from misreading the response.

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?

Three short sentences, with the primary purpose front-loaded and no filler. The conditional example earns its place by resolving a likely misreading.

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 query with an output schema, the description covers what the tool returns, when to call it, and a non-obvious output field interaction. Nothing essential for invoking 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%, and the ticker schema description is rich (case-insensitivity, prefix conventions, bare BTC/ETH are ETFs). The main description adds no additional parameter semantics, so the baseline 3 is appropriate.

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?

Opens with 'For one ticker, what we hold and how far back,' which names the resource (one ticker's coverage) and the specific output (coverage depth/history). The empty-result clarification distinguishes it from data-retrieval siblings like get_bars/get_series, so an agent can route correctly.

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?

Explicitly instructs: 'Ask this before treating a gap in bars or series as an outage,' a concrete when-to-use condition. It doesn't name the sibling tools to avoid, but the reference to bars/series is sufficient context.

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.