AudioAlpha

get_market_featured_quotes

Get the top featured quotes from crypto podcasts for a given date, ranked by relevance score.

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. Dates show when Glama detected each change.

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.5/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the behavioral burden. It mentions ranking by relevance, but does not disclose response shape, pagination, default date behavior, or what happens when no data exists. The schema provides parameter details, but the description itself adds little 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?

Single, front-loaded sentence with no filler. Every word contributes to the purpose, and it is 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.

Completeness3/5

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

The tool has 4 parameters and no output schema, yet the description does not hint at response structure or pagination. It is minimally viable given the rich parameter schema, but leaves gaps about return values and edge-case behavior.

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 does not add meaning beyond the schema—saying 'for a given date' merely echoes the 'date' parameter description. The rich schema already documents defaults and enum values.

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?

Description uses specific verb 'Get' and clearly identifies the resource: 'top featured quotes from crypto podcasts'. It adds scoping details ('for a given date', 'ranked by relevance score') that distinguish it from sibling tools like get_ticker_featured_quotes.

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?

Usage context is implied—this tool gets market-level featured quotes—but no explicit guidance is given about when to choose it over alternatives like get_ticker_featured_quotes. There is no mention of exclusions or fallbacks.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation5/5

Every tool targets a distinct resource and data aspect: episode details, quotes, transcript, summary, market snapshots, ticker history, user feeds, etc. Even the 'full' composite variants are clearly described as one-call conveniences that bundle granular data, so there is no real ambiguity about which tool to use.

Naming Consistency5/5

All 23 tools follow a consistent 'get_<entity>_<detail>' pattern using lowercase snake_case. This uniformity makes the tool names predictable and mentally indexed, with no mixing of verb styles or naming conventions.

Tool Count3/5

With 23 tools, the server sits in the 'heavy' range (16–25) and feels a bit bloated. The breadth of resources justifies many endpoints, but several composite 'full' versions and overlapping history functions inflate the count and could be consolidated without losing capability.

Completeness4/5

The read-only surface covers core workflows well: episode-level detail, podcast discovery, market-wide snapshots/history/themes, ticker-specific data/leaderboards, and user personalization. Minor gaps include no way to enumerate all supported tickers or podcasts beyond search, and no direct episode list by date without going through the market endpoint.

Resources

Need Help?