Skip to main content
Glama

AudioAlpha

by io.audioalpha
OverviewDiscussionsAdmin

get_ticker_history

Fetch a historical time series of daily snapshots for one crypto ticker. Call this when the user asks about a ticker's recent trend, wants to chart or plot α-sentiment / α-index / α-pulse over time, asks "how has X changed over the last N days", or needs a window of data to compute averages, momentum, or volatility.

Required: ticker — MUST be suffixed with "-USD" (e.g. "BTC-USD", "ETH-USD", "SOL-USD"). Bare symbols like "BTC" will not match. Optional: days (1-1000, default 30; tier may cap lower).

Tier caps on days: free=7, alpha=365, pro=730, enterprise=1000.

The date parameter (end-date anchor) is only honored for enterprise tier — for all other tiers it is silently ignored and the window always ends at the most recent available snapshot. This is by design to prevent back-testing on arbitrary historical periods on lower tiers.

Returns: array of daily snapshots (oldest first), each with snapshot_date plus all standard AssetSnapshot fields. Response also reports tier_cap, effective_days, start_date, end_date and date_param_honored.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate in YYYY-MM-DD format. Omit for latest.
daysNoNumber of historical days to return, counting back from the anchor date. Tier-capped: free=7, alpha=365, pro=730, enterprise=1000. Requests above the cap are silently capped.
tickerYesAsset ticker symbol. IMPORTANT: all crypto tickers MUST be suffixed with "-USD" — e.g. BTC-USD, ETH-USD, SOL-USD. Bare symbols like "BTC" will not match and will return an empty / 404 response.
version_infoNoWhen true, include version metadata in the response: both version_num (the revision number) and version_label (a human-readable label like "eod_utc" for the initial end-of-day build, or "revised" when a later-indexed podcast triggered a regeneration). When false (the default), neither field is included. Note: the snapshot generation "status" field is ALWAYS returned regardless of this flag.
snapshot_typeNoAsset universe to draw the snapshot from. Currently only "crypto" is available; "tradfi" is reserved for a future release. Defaults to "crypto".crypto

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / version_info / description
      Previous value: -"When true, include version metadata in the response: both version_num (the revision number) and version_label (a human-readable label like \"eod_utc\", \"backfill\", \"revised\"). When false (the default), neither field is included."New value: +"When true, include version metadata in the response: both version_num (the revision number) and version_label (a human-readable label like \"eod_utc\" for the initial end-of-day build, or \"revised\" when a later-indexed podcast triggered a regeneration). When false (the default), neither field is included. Note: the snapshot generation \"status\" field is ALWAYS returned regardless of this flag."
  2. Changed1 schema field changed
    • changedInput schema / properties / version_info / description
      Previous value: -"When true, include the human-readable version_label (e.g. \"eod_utc\", \"backfill\", \"revised\") alongside the always-present version_num in the response. Defaults to false."New value: +"When true, include version metadata in the response: both version_num (the revision number) and version_label (a human-readable label like \"eod_utc\", \"backfill\", \"revised\"). When false (the default), neither field is included."
  3. Changed2 schema fields changed
    • addedInput schema / properties / snapshot_type
      Added value: +{
+  "default": "crypto",
+  "description": "Asset universe to draw the snapshot from. Currently only \"crypto\" is available; \"tradfi\" is reserved for a future release. Defaults to \"crypto\".",
+  "enum": [
+    "crypto",
+    "tradfi"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / version_info
      Added value: +{
+  "default": false,
+  "description": "When true, include the human-readable version_label (e.g. \"eod_utc\", \"backfill\", \"revised\") alongside the always-present version_num in the response. Defaults to false.",
+  "type": "boolean"
+}
  4. Changed1 schema field changed
    • changedInput schema / properties / ticker / description
      Previous value: -"Asset ticker symbol e.g. BTC, ETH, SOL"New value: +"Asset ticker symbol. IMPORTANT: all crypto tickers MUST be suffixed with \"-USD\" — e.g. BTC-USD, ETH-USD, SOL-USD. Bare symbols like \"BTC\" will not match and will return an empty / 404 response."
  5. Added

TDQS

A4.8/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 of behavioral disclosure, and it delivers richly. It reveals that `date` is silently ignored for non-enterprise tiers, `days` is silently capped, bare ticker symbols return empty/404, and the response includes tier_cap, effective_days, start_date, end_date, and date_param_honored. It even explains the version_info behavior and that the status field is always returned. This is exemplary transparency.

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?

The description is well-structured and front-loaded. The first sentence defines the core action, followed by explicit use-case guidance, then clear parameter requirements, tier caps, date behavior, and return format. Every sentence adds necessary information without redundancy or fluff, making it appropriately sized for the tool's complexity.

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?

Despite lacking an output schema, the description adequately describes the return format: 'array of daily snapshots (oldest first), each with snapshot_date plus all standard AssetSnapshot fields' and lists the response metadata fields. It also covers parameter edge cases (bare symbols, tier caps, date honoring). The description is complete enough for an agent to invoke the tool correctly and set expectations for the response without any additional documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds significant semantic value beyond the schema. It explains the '-USD' suffix requirement in detail, clarifies that the `date` parameter is only honored for enterprise tier (silently ignored otherwise), specifies that `days` is tier-capped and silently capped, and elaborates on `version_info` fields and `snapshot_type` reserved 'tradfi' status. This goes well beyond the schema's basic descriptions.

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?

The description opens with a specific verb+resource+scope: 'Fetch a historical time series of daily snapshots for one crypto ticker.' It clearly distinguishes the tool from siblings like get_ticker_snapshot (current snapshot) and get_market_history (market-wide) by focusing on per-ticker historical data. The use-cases ('recent trend', 'chart', 'averages, momentum, or volatility') further reinforce the specific purpose.

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?

The description explicitly states when to call the tool: 'Call this when the user asks about a ticker's recent trend... or needs a window of data to compute averages, momentum, or volatility.' This is clear context for invocation. However, it does not explicitly name alternatives or when-not-to-use, though the sibling tool names imply the distinction. Thus, it earns a 4 for clear context lacking explicit exclusions.

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

All AudioAlpha toolsInspect
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.

Resources