Skip to main content
Glama

AudioAlpha

by io.audioalpha
OverviewDiscussionsAdmin

get_ticker_signals

Get scenario signals for a specific crypto asset. Returns signal type, time horizon, scenario description, trigger conditions, confidence score and invalidating conditions. (Not financial advice.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate in YYYY-MM-DD format. Omit for latest.
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
version_numberNoWhich revision of the snapshot to return. Each snapshot date can be re-generated multiple times (version 1, 2, 3, …). Use -1 (the default) to always get the latest authoritative version (is_latest = true). If you request a specific version that does not exist for the given date + snapshot_type, the latest version is returned instead.

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. Changed3 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"
+}
    • addedInput schema / properties / version_number
      Added value: +{
+  "default": -1,
+  "description": "Which revision of the snapshot to return. Each snapshot date can be re-generated multiple times (version 1, 2, 3, …). Use -1 (the default) to always get the latest authoritative version (is_latest = true). If you request a specific version that does not exist for the given date + snapshot_type, the latest version is returned instead.",
+  "minimum": -1,
+  "type": "integer"
+}
  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. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does reveal the acceptable return fields and implicitly indicates a read-only operation via 'Get'. However, it does not disclose edge-case behaviors like fallback to the latest version for invalid versions, empty/404 responses for invalid tickers, or that the 'status' field is always returned—though some of these are covered in parameter descriptions. The 'Not financial advice' disclaimer is not behavioral context.

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 two sentences with no redundancy. The first sentence states the purpose and scope, the second lists output components. The disclaimer is slightly extraneous but does not detract from conciseness or structure.

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

Completeness4/5

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

Given the absence of an output schema, the description helpfully enumerates the returned signal attributes, which is important for the agent. The parameter schema handles the parameter-side complexity well. The only notable gaps are the lack of explicit usage alternatives and edge-case behavior, but for a read-only signal retrieval tool with a rich schema, the description is largely complete.

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?

The input schema provides 100% parameter coverage with detailed descriptions, including the mandatory '-USD' suffix and version fallback semantics. The tool description adds no parameter-level information beyond the schema, 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?

The description uses a specific verb ('Get') and resource ('scenario signals for a specific crypto asset'), clearly distinguishing it from market-level siblings like get_market_signals. It also enumerates what the tool returns (signal type, time horizon, scenario description, trigger conditions, confidence score, invalidating conditions), leaving no ambiguity about its function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'for a specific crypto asset' implies the tool is for ticker-level signals, but the description offers no explicit guidance on when to use it versus alternatives such as get_market_signals or get_ticker_snapshot. It also does not mention exclusions or prerequisites, so the usage context remains only implied.

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