Skip to main content
Glama
Sign In
AuraStream MCP

AuraStream MCP

by UnbiasedAlpha
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_latest

Read-onlyIdempotent

Fetch a configurable number of recent OHLCV bars per ticker without choosing dates; useful for delayed market snapshots where the final bar may still form.

Instructions

Return the most recent N bars (OHLCV) per ticker, without having to pick dates. Uses one unit of the monthly AuraStream allowance. Data is historical/delayed, not a live quote; the last bar may still be forming.

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": {
      "source": "<source>",
      "tickers": "<tickers>"
    },
    "name": "get_latest"
  }
}

Input Schema

NameRequiredDescriptionDefault
barsNoHow many of the most recent bars to return per ticker.
sourceYesData source id, see list_sources.
tickersYesTickers in the source's own format.
intervalNoBar size, e.g. 1h or 1d.1d

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.7
    • changedInput schema / properties / source / enum
      Previous value: -[
-  "binance",
-  "bybit",
-  "kraken",
-  "deribit",
-  "kucoin",
-  "dydx",
-  "hyperliquid",
-  "lyra",
-  "coinapi",
-  "coingecko",
-  "nemeton",
-  "yahoo",
-  "firstrate",
-  "oanda",
-  "alpaca",
-  "polygon",
-  "tradestation",
-  "cityindex",
-  "fred",
-  "finnhub",
-  "worldbank",
-  "eia",
-  "treasury",
-  "sdmx",
-  "nasdaq",
-  "econcalendar",
-  "bea",
-  "tradingeconomics",
-  "cftc",
-  "edgar",
-  "hmrc",
-  "comext",
-  "uscensus",
-  "hktrade",
-  "defillama",
-  "gdelt",
-  "openmeteo",
-  "visualcrossing",
-  "tsa",
-  "netshort",
-  "wasde",
-  "warn",
-  "degreedays",
-  "fedtext",
-  "usaspending"
-]New value: +[
+  "binance",
+  "bybit",
+  "kraken",
+  "deribit",
+  "kucoin",
+  "dydx",
+  "hyperliquid",
+  "lyra",
+  "coinapi",
+  "coingecko",
+  "nemeton",
+  "yahoo",
+  "firstrate",
+  "oanda",
+  "alpaca",
+  "polygon",
+  "tradestation",
+  "cityindex",
+  "fred",
+  "finnhub",
+  "worldbank",
+  "eia",
+  "treasury",
+  "sdmx",
+  "nasdaq",
+  "econcalendar",
+  "bea",
+  "tradingeconomics",
+  "cftc",
+  "edgar",
+  "hmrc",
+  "comext",
+  "uscensus",
+  "hktrade",
+  "defillama",
+  "gdelt",
+  "openmeteo",
+  "visualcrossing",
+  "tsa",
+  "netshort",
+  "wasde",
+  "warn",
+  "degreedays",
+  "fedtext",
+  "usaspending",
+  "signals"
+]
  2. Changed1 schema field changedv0.1.6
    • changedInput schema / properties / source / enum
      Previous value: -[
-  "binance",
-  "bybit",
-  "kraken",
-  "deribit",
-  "kucoin",
-  "dydx",
-  "hyperliquid",
-  "lyra",
-  "coinapi",
-  "coingecko",
-  "nemeton",
-  "yahoo",
-  "firstrate",
-  "oanda",
-  "alpaca",
-  "polygon",
-  "tradestation",
-  "cityindex",
-  "fred",
-  "finnhub",
-  "worldbank",
-  "eia",
-  "treasury",
-  "sdmx",
-  "nasdaq",
-  "econcalendar",
-  "bea",
-  "tradingeconomics",
-  "cftc",
-  "edgar",
-  "hmrc",
-  "comext",
-  "uscensus",
-  "hktrade",
-  "defillama",
-  "gdelt",
-  "openmeteo",
-  "visualcrossing",
-  "tsa"
-]New value: +[
+  "binance",
+  "bybit",
+  "kraken",
+  "deribit",
+  "kucoin",
+  "dydx",
+  "hyperliquid",
+  "lyra",
+  "coinapi",
+  "coingecko",
+  "nemeton",
+  "yahoo",
+  "firstrate",
+  "oanda",
+  "alpaca",
+  "polygon",
+  "tradestation",
+  "cityindex",
+  "fred",
+  "finnhub",
+  "worldbank",
+  "eia",
+  "treasury",
+  "sdmx",
+  "nasdaq",
+  "econcalendar",
+  "bea",
+  "tradingeconomics",
+  "cftc",
+  "edgar",
+  "hmrc",
+  "comext",
+  "uscensus",
+  "hktrade",
+  "defillama",
+  "gdelt",
+  "openmeteo",
+  "visualcrossing",
+  "tsa",
+  "netshort",
+  "wasde",
+  "warn",
+  "degreedays",
+  "fedtext",
+  "usaspending"
+]
  3. Changed2 schema fields changedv0.1.4
    • changedInput schema / properties / interval / enum
      Previous value: -[
-  "1s",
-  "5s",
-  "10s",
-  "15s",
-  "30s",
-  "1M",
-  "2M",
-  "3M",
-  "5M",
-  "10M",
-  "15M",
-  "30M",
-  "1h",
-  "2h",
-  "4h",
-  "6h",
-  "8h",
-  "12h",
-  "1d",
-  "3d",
-  "5d",
-  "1w",
-  "1m",
-  "1q",
-  "1y"
-]New value: +[
+  "1s",
+  "5s",
+  "10s",
+  "15s",
+  "30s",
+  "1M",
+  "2M",
+  "3M",
+  "4M",
+  "5M",
+  "10M",
+  "15M",
+  "30M",
+  "60M",
+  "90M",
+  "1h",
+  "2h",
+  "3h",
+  "4h",
+  "6h",
+  "8h",
+  "12h",
+  "1d",
+  "3d",
+  "5d",
+  "1w",
+  "1m",
+  "3m",
+  "1q",
+  "1y"
+]
    • changedInput schema / properties / source / enum
      Previous value: -[
-  "binance",
-  "bybit",
-  "kraken",
-  "yahoo",
-  "firstrate",
-  "oanda",
-  "alpaca",
-  "polygon",
-  "fred",
-  "finnhub",
-  "worldbank",
-  "eia",
-  "treasury",
-  "cftc",
-  "finra",
-  "edgar",
-  "hmrc",
-  "comext",
-  "uscensus",
-  "hktrade",
-  "defillama",
-  "gdelt"
-]New value: +[
+  "binance",
+  "bybit",
+  "kraken",
+  "deribit",
+  "kucoin",
+  "dydx",
+  "hyperliquid",
+  "lyra",
+  "coinapi",
+  "coingecko",
+  "nemeton",
+  "yahoo",
+  "firstrate",
+  "oanda",
+  "alpaca",
+  "polygon",
+  "tradestation",
+  "cityindex",
+  "fred",
+  "finnhub",
+  "worldbank",
+  "eia",
+  "treasury",
+  "sdmx",
+  "nasdaq",
+  "econcalendar",
+  "bea",
+  "tradingeconomics",
+  "cftc",
+  "edgar",
+  "hmrc",
+  "comext",
+  "uscensus",
+  "hktrade",
+  "defillama",
+  "gdelt",
+  "openmeteo",
+  "visualcrossing",
+  "tsa"
+]
  4. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Adds substantial context beyond the read-only/idempotent annotations: it consumes one unit of the monthly AuraStream allowance, the data is historical/delayed rather than a live quote, and the last bar may still be forming. These are exactly the quirks an agent needs before calling.

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 tight sentences, front-loaded with what is returned, followed by quota and data-freshness caveats. No filler.

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?

Output schema exists, all four parameters are documented, and the description covers the non-obvious concerns (cost, delay, partial last bar). Nothing an agent needs to invoke 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 description coverage is 100% – bars, source, tickers, and interval are all documented in-schema. The description's 'N bars per ticker' restates the schema rather than adding format or edge-case meaning, so baseline 3 applies.

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: return the most recent N OHLCV bars per ticker. 'Without having to pick dates' implicitly contrasts with get_timeseries, though the sibling is never named outright.

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?

Gives a clear selection condition – use this when you don't want to specify dates – which is exactly what separates it from get_timeseries. No explicit exclusions or named alternatives, so it falls short of a 5.

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

Deploy Server

Other Tools