Skip to main content
Glama

AudioAlpha

by io.audioalpha
OverviewDiscussionsAdmin

get_ticker_leaderboard

Get ticker leaderboard for a given date. Without category param, returns highlights object that includes assetSnapshot of top_alpha_index, top_alpha_pulse, top_riser, top_dropper, most_mentioned, most_surprising. With category param (alpha_index/alpha_pulse/risers/droppers/mentioned/surprising), returns array of LeaderboardEntry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate in YYYY-MM-DD format. Omit for latest.
limitNoNumber of episodes to return (max 20, default 5)
categoryNoLeaderboard category: alpha_index, alpha_pulse, risers, droppers, mentioned, or surprising. Omit for highlights (top 1 from each).
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. First observed

TDQS

A4/5.0
Behavior3/5

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

There are no annotations provided, so the description carries the full burden of behavioral disclosure. It does explain the two response shapes depending on the category parameter, which is useful. However, it omits details about potential side effects, rate limits, error behavior, or the impact of other parameters like date omission and limit. For a read-only getter, this is adequate but not comprehensive.

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, front-loaded with the core purpose, and directly conveys both modes of operation without any redundant phrasing. Every sentence earns its place, providing high information density in a compact 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 that there is no output schema, the description usefully specifies the return shape for both modes. It covers the main complexity of the tool (category-dependent behavior) but does not mention defaults for date or limit, though those are covered in the schema. Overall, it is sufficiently complete for the tool's moderate complexity.

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 adds value specifically for the category parameter by explaining the two possible return formats. It does not add additional semantics for date, limit, version_info, or snapshot_type beyond what the schema already documents. Thus, it meets but does not exceed the baseline.

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 starts with a specific verb+resource+time: 'Get ticker leaderboard for a given date.' It clearly distinguishes itself from sibling ticker tools by focusing on leaderboard rankings. It further specifies the two operational modes based on the category parameter, leaving no ambiguity about what the tool returns.

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 provides clear context: use this tool to retrieve ticker leaderboards for a date, with or without a category filter. It explains the difference between calling without category (returns highlights) and with category (returns an array). However, it does not explicitly state when to choose this over sibling tools like get_ticker_snapshot or get_ticker_history, nor does it mention 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