AudioAlpha

get_market_snapshot

Get the overall crypto market daily snapshot (daily narrative insight report) for a given date. Returns daily headline, delta narrative, regime + justification, α-sentiment OHLC scores (0-10 scale), α-sentiment z-scores (-3 to +3), narrative summary, narrative intesity score, market psychology, consensus score, key tensions, surprise mentions (ticker + why + impact score), episode volume score, and wordcloud.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	No	Date in YYYY-MM-DD format. Omit for latest.
`version_info`	No	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.
`snapshot_type`	No	Asset universe to draw the snapshot from. Currently only "crypto" is available; "tradfi" is reserved for a future release. Defaults to "crypto".	crypto
`version_number`	No	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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJun 23, 2026

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."

Changed1 schema field changedJun 15, 2026

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."

Changed3 schema fields changedJun 12, 2026

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"
+}

First observedApr 13, 2026

TDQS

A3.9/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 lists the many return fields but does not mention behaviors like date defaulting to latest when omitted, the fallback for version_number, or the fact that snapshot_type currently only supports 'crypto'. These are covered in the schema, but the description adds no behavioral caveats beyond the output list.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence that efficiently states the tool's purpose and enumerates valuable return fields. It is slightly long and contains a typo ('intesity'), but every part contributes useful information given there is no output schema.

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 tool's simplicity, the rich schema documentation for parameters, and the absence of an output schema, the description provides a thorough list of return fields that helps the agent anticipate the response. However, it slightly implies date is required when it is optional, which is a minor gap in completeness.

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%, so the baseline is 3. The description only indirectly references the 'date' parameter by saying 'for a given date' and adds no additional meaning to the parameters beyond what the schema already explains.

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 clearly states the tool gets an 'overall crypto market daily snapshot' for a given date, with a specific verb and resource. It distinguishes itself from sibling tools like get_market_history, get_market_signals, and get_ticker_snapshot by focusing on the daily narrative report.

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 implies usage for retrieving a daily market narrative report for a specific date, which provides clear context. However, it does not explicitly mention alternatives or when not to use this tool, such as pointing to get_market_themes or get_market_history for other data needs.

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

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

Resources

Need Help?