{"id":96788,"plugin_id":"plugin_asdk_app_6a75b3c25e848191a9b44c892a4b3120","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-14T18:09:18.735Z","digest":"22e8acf0c2faf2a3bb36d07870f4d2a1cc9601a57cccfac79f3c9fd657727580","against":null,"payload":{"description":"Query latest and historical market data through the TickerLayer MCP server, including quotes, snapshots, OHLCV history, symbol discovery, market hours and holidays, government bond yields and an interactive markets board, across crypto, forex, stocks, indices, ETFs, commodities and perpetual futures. Use whenever the user asks about a price, a market move, an exchange rate, candle or chart history, whether a market is open, a bond yield, or a market overview, and the TickerLayer tools (get_snapshot, get_history, list_symbols, open_markets_board, and the rest) are available.","included_files":[{"relative_path":"references/api-notes.md","size_in_bytes":10999}],"name":"market-data","skill_md_contents":"---\nname: market-data\ndescription: Query latest and historical market data through the TickerLayer MCP server, including quotes, snapshots, OHLCV history, symbol discovery, market hours and holidays, government bond yields and an interactive markets board, across crypto, forex, stocks, indices, ETFs, commodities and perpetual futures. Use whenever the user asks about a price, a market move, an exchange rate, candle or chart history, whether a market is open, a bond yield, or a market overview, and the TickerLayer tools (get_snapshot, get_history, list_symbols, open_markets_board, and the rest) are available.\n---\n\n# TickerLayer Market Data\n\nAnswer market questions with the TickerLayer MCP tools. The tools are the\ncomplete surface. Never construct or guess REST URLs. If a call fails, report\nwhat failed instead of filling the gap with remembered or estimated prices.\n\n## Picking the right tool\n\n| Question shape | Tool |\n| --- | --- |\n| \"How is X doing?\" Last price and change against the previous close in one call | `get_snapshot` |\n| Current bid/ask spread | `get_quote` |\n| Most recent trade (price, size, time) | `get_last_trade` |\n| A confirmed close: yesterday's daily bar, or the latest settled intraday bar | `get_previous_close` |\n| Chart data, ranges, \"over the last month\" | `get_history` |\n| \"What symbols do you have?\" or resolving a fuzzy name | `list_symbols` |\n| \"Is the market open?\" | `get_market_status` |\n| Trading hours and session times | `get_market_sessions` |\n| Upcoming or past market holidays | `get_market_holidays` |\n| Government bond yields (US:10Y, DE:10Y, ...) | `get_bond_yield` |\n| A broad market overview, or \"open TickerLayer\" | `open_markets_board` |\n\n`search_symbols` powers the search box inside the markets board. Use\n`list_symbols` for your own lookups.\n\nRules of thumb:\n\n- **Every data tool needs `asset_class` as well as `symbol`.** `get_quote`,\n  `get_last_trade`, `get_snapshot`, `get_previous_close` and `get_history` all\n  require `asset_class`, one of `crypto`, `forex`, `stocks`, `indices`, `etfs`,\n  `commodities`, `perpetuals`. Choose it deliberately: `XAUUSD` is commodities,\n  `EURUSD` is forex, `XAUUSDT` is perpetuals, and a wrong class resolves to the\n  wrong instrument or a 404.\n- **`get_snapshot` is the best single call** for \"how is X doing\". It bundles\n  the last price, bid and ask, the previous close, and the change and percent\n  change. Prefer it over stitching `get_quote` and `get_previous_close`\n  together. `get_quote` returns only bid, ask and sizes, so it is not the tool\n  for \"what's the price\".\n- **`get_previous_close` with `interval`** returns the latest fully settled bar\n  of that interval (for example the last completed 1-hour bar), not only\n  yesterday's daily close. The values are exactly `1m`, `5m`, `15m`, `1h`,\n  `4h`, `1d`. Omit it for the previous daily bar. Use it when the user wants a\n  confirmed, non-live value.\n- **`get_history` has no `interval` parameter.** The bar size is `multiplier`\n  plus `timespan`: `1`, `5` or `15` with `minute`; `1` or `4` with `hour`; `1`\n  with `day`. No other pair is valid. `from` and `to` are UTC dates in\n  `YYYY-MM-DD`. `limit` (default 500, max 5000) and `sort` (`asc` or `desc`,\n  default `desc`) are optional.\n- **One `get_history` request covers a limited span**, and the span is shorter\n  for smaller bars. A range that is too large returns a 400 that names the\n  maximum, so split it into consecutive requests. A non-null `next_offset`\n  means more bars matched than `limit` returned: raise `limit` or narrow the\n  dates.\n- **Bonds go through `get_bond_yield` only.** The value is a yield in percent,\n  not a price, and it is a daily observation. Do not ask the quote tools for\n  bond symbols.\n- **`open_markets_board` costs ten requests**, one per row, on the user's plan\n  (Bitcoin, Ethereum, Solana, EUR/USD, USD/JPY, GBP/USD, gold, silver, Nvidia\n  and Tesla; its search box reaches every other instrument),\n  and each chart, search or refresh inside the board costs more. Use it for\n  overviews or when the user asks for TickerLayer itself. For one instrument,\n  call `get_snapshot`. Where the client cannot show the\n  interactive board, the tool returns the same rows as a text summary: present\n  them as a short table.\n\n## Symbol conventions\n\n| Asset class | Format | Examples |\n| --- | --- | --- |\n| Crypto | pair, no separator | `BTCUSD`, `ETHUSD` |\n| Forex | pair, no separator | `EURUSD`, `USDJPY` |\n| Commodities | pair-style code | `XAUUSD` (gold), `XAGUSD` (silver), `WTIUSD` (WTI oil) |\n| Indices | region plus number | `US500`, `US30`, `DE40`, `UK100`, `JP225` |\n| ETFs | catalog codes and listing tickers | `US500ETF`, `USGOLD`, `SPY` |\n| Stocks | **always** `COUNTRY:TICKER` (ISO alpha-2) | `US:KO`, `DE:SAP`, `SA:2222` |\n| Perpetual futures | USDT-quoted contract | `BTCUSDT`, `XAUUSDT`, `KOUSDT` |\n| Bonds | `COUNTRY:TENOR` (`DE`, `ES`, `FR`, `IT`, `UK`, `US`) | `US:10Y`, `DE:10Y`, `US:3M`, `UK:2Y` |\n\nA code ending in `USDT` is always a perpetual contract, never a crypto pair:\nspot Bitcoin is `BTCUSD` (crypto), the perpetual is `BTCUSDT` (perpetuals).\nUS-listed funds are ETFs, not stocks: `SPY` goes to `etfs`, never `US:SPY`\nunder `stocks`.\n\nThe country prefix on stocks is mandatory. `KO` alone is not a valid\nTickerLayer stock symbol; it is `US:KO`. When the user gives a bare ticker,\ninfer the market from context or confirm through discovery (below). Default to\nUS only when the ticker is unambiguously a US listing.\n\nIndex names in the catalog are neutral and descriptive, such as US 500,\nGermany 40 or Japan 225. When a user names an index by a brand, map it to the\nneutral code by region and size, or search with\n`list_symbols(asset_class=\"indices\", search=\"US\")`, and answer with the\nneutral code and name.\n\nBond country codes are their own set: UK gilts are `UK:10Y`, **not** `GB:10Y`\n(which 404s), even though the market calendar tools use `GB` (or `UK`) for the\nLondon market.\n\nPerpetual futures trade around the clock, including weekends. Each contract\nhas one composite quote, and `get_snapshot` adds a `mark_price`. They need the\nPerpetuals plan.\n\n## Discovery first\n\nCall `list_symbols` before guessing a symbol. Guessing wastes calls and\nproduces confident wrong answers when a guess happens to match a different\ninstrument.\n\n- `asset_class` is required, so decide what kind of instrument the user means\n  (\"Coca-Cola stock\" means stocks, \"gold\" means commodities, \"the US 500\"\n  means indices). Narrow with the optional `search` substring, matched\n  case-insensitively against symbol and name, and `limit` (max 500, default\n  100). There is no `market` parameter: approximate a country filter with a\n  prefix search such as `search=\"DE:\"`.\n- When the phrasing is ambiguous, list the candidates and pick the one that\n  matches intent. \"Gold\" can be the commodity `XAUUSD`, the fund `USGOLD` or\n  the perpetual `XAUUSDT`; \"the US 500\" can be the index `US500` or the fund\n  `US500ETF`. Use the index for \"how did the market do\" and the fund only when\n  the user asks about the tradable fund.\n- For stocks, `list_symbols` lists the markets the user's plan includes, so an\n  empty result can mean the market is not in the plan. Say so instead of\n  substituting a look-alike from another market.\n\n## Market calendar before \"no data\"\n\nA quiet symbol is usually a closed market, not an error. Before telling the\nuser that data looks stale or missing:\n\n1. Call `get_market_status` for the relevant market.\n2. If it is closed, say so and present the last available data as the close,\n   with its timestamp.\n3. Use `get_market_sessions` for exact open and close times and\n   `get_market_holidays` when \"why is it closed on a weekday\" comes up. Both\n   need `market` or `symbol`.\n\nCrypto and perpetual futures trade continuously; forex closes on weekends;\nstock and index hours vary by country. Perpetual futures have no market\ncalendar, so the calendar tools do not take them. Never read a weekend forex\nor holiday stock value as an outage.\n\n## Timestamps\n\nData tools return timestamps as Unix **milliseconds**. In the market calendar\ntools, session start and end, `next_open` and `next_close` are ISO 8601 UTC\nstrings, `local_time` uses the market's own offset, and dates (holidays, and\nthe `date` you pass to `get_market_sessions`) are the market's local dates.\n`get_history` `from` and `to` are plain UTC dates (`YYYY-MM-DD`), and a bond's\n`date` is its observation day. When you show a time to the user, convert it to\na readable time and state the timezone you chose.\n\n## Error handling\n\n- **400**: the request is invalid. The message says what to fix, such as an\n  unsupported bar size, a range that is too large, or an unknown market code.\n  Fix the parameter and try once more.\n- **401**: no valid credentials. Ask the user to connect their TickerLayer\n  account or configure an API key. Do not retry.\n- **403**: the account cannot read this data. Usually the plan does not\n  include it (an asset class, a market, or perpetual futures); it can also\n  mean a package has expired or a key is suspended. Relay the message. Do\n  **not** invent endpoints, try look-alike symbols to get around it, or retry\n  repeatedly.\n- **404 or empty**: when the answer names the asset class and symbol to call\n  again with (an ETF asked as a stock, an index asked as a forex pair, a bond\n  asked as a stock), make that call once. Otherwise check the symbol with\n  `list_symbols` and the calendar with `get_market_status` before concluding\n  the data is missing. A quiet perpetual\n  contract can return 404 for its last trade while its quote is fine.\n- **429**: either the per-second rate limit (slow down and reduce polling) or\n  the monthly quota (`REST_QUOTA_EXCEEDED`), which slowing down does not fix:\n  the allowance renews in the next period. Relay that plainly; the plans are\n  described at https://tickerlayer.com/pricing.\n- **503**: data is temporarily unavailable. Say so, and try again later rather\n  than in a loop.\n\n## How to present the data\n\nEvery substantive market answer reflects TickerLayer's positioning:\n\n- The data is **derived and indicative**: aggregated, not official exchange\n  prints. Present prices as TickerLayer data, never as official exchange\n  prices.\n- Add a brief note on figures a user might act on, for example \"Prices are\n  indicative and may differ from official exchange values.\"\n- **No investment advice.** Report data, trends and facts. Do not recommend\n  buying, selling or holding anything. If asked for advice, say you can\n  provide data but not recommendations.\n\n## Playbooks for common requests\n\n**\"What's the price of X?\"**\n1. Resolve the symbol (`list_symbols` if it is not obvious).\n2. `get_snapshot`: quote `last_price` with its `last_timestamp` and the change\n   against `prev_close`. If `last_price` is null, report the bid and ask.\n3. If the market is closed, label the number as the last close, not\n   \"current\".\n\n**\"How did X do this week or month?\"**\n1. `get_history` with `multiplier=1`, `timespan=\"day\"`, `sort=\"asc\"` and\n   `from`/`to` covering the range. Without `sort=\"asc\"` the newest bar comes\n   first.\n2. Compute the change from the first open to the last close yourself and state\n   both dates so the user knows exactly what was measured.\n3. A range that includes today ends with a bar that is still forming. Use\n   `get_previous_close` for a confirmed close and `get_snapshot` for \"today so\n   far\".\n\n**\"Compare X and Y.\"**\n1. One `get_snapshot` per symbol.\n2. Compare percent change, not absolute price. Mention when the two trade on\n   different calendars (for example crypto against a stock on a market\n   holiday).\n\n**\"Give me a confirmed close for X at interval N.\"**\n1. `get_previous_close` with `interval` (`1m`, `5m`, `15m`, `1h`, `4h`, `1d`).\n   Never derive a close from a live quote or a bar that is still forming.\n\n**\"Why is X flat or not updating?\"**\n1. `get_market_status` first. A closed market is expected: say when it reopens\n   (`get_market_sessions`, `get_market_holidays`).\n2. Only if the market is open and the data is stale, report a data issue.\n\n**\"What's the 10-year yield?\"**\n1. `get_bond_yield` with `COUNTRY:TENOR` (`US:10Y` unless another country is\n   implied). Present it as a percentage yield, not a price.\n\n**\"How are the markets doing?\" or \"Open TickerLayer.\"**\n1. `open_markets_board`. The user sees the values on the board, so summarize\n   the notable moves instead of repeating every number.\n2. For follow-ups about one instrument, use `get_snapshot` or `get_history`.\n\n**\"What is gold doing on the weekend?\"**\n1. `get_snapshot` with `asset_class=\"perpetuals\"` and `symbol=\"XAUUSDT\"`. The\n   perpetual trades while the commodity market is closed; say which one you\n   quoted.\n\nPrecision: quote prices at the precision the API returns. Do not round crypto\nor forex to two decimals. Attach the data's timestamp whenever the user is\nmaking time-sensitive comparisons.\n\n## Going deeper\n\nFor the full parameter reference (bar sizes, limits, sort, market codes, the\n`include_sessions` and `include_holiday` flags on `get_market_status`, bond\ntenor coverage and perpetual futures), read\n[references/api-notes.md](references/api-notes.md).\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}