OffStereo

Discover music

discover

Read-onlyIdempotent

Discover genre-aware new releases, strong public-archive matches, or popular OffStereo shows. Call exactly once per listener request: put every positive genre into the same genres array, use [] when none were requested, and avoid one call or card per genre. query carries the listener's full wording, exclusions, counts, and no-padding constraint. Results remain relevant rather than padding a requested genre or archive search with unrelated rows. Dated music-history requests use music_today and are not a discover mode. playableOnly limits results to music that plays in ChatGPT. allowBuild and allowSave preserve a read-only request. The result card already includes song playback; a separate one-song card is for an explicit request for a dedicated song card.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "type": "<type>",
      "genres": "<genres>"
    },
    "name": "discover"
  }
}

Input Schema

Name	Required	Description
`type`	Yes	Discovery mode. trending returns the pre-built fresh surface: the Friday Rundown, this week's records and today's anniversary, chart and news stories, every one already built and playable; search aliases archive; dated music-history requests use music_today.
`limit`	No	Maximum total results (1-20).
`query`	No	Archive query, or the listener's release-discovery wording when it contains genres, balance, count, or no-padding constraints.
`genres`	Yes	Every positively requested genre; [] when the request is not genre-filtered. Results do not pad with unrelated genres.
`allowSave`	No	False preserves an explicit request not to create or save anything.
`allowBuild`	No	False preserves an explicit request not to create or build a story.
`playableOnly`	No	True limits results to music with audio that plays inside ChatGPT.
`perGenreLimit`	No	Maximum results from each named genre for a balanced new-release request.

Output Schema

Name	Required	Description
`id`	No
`date`	No	ISO date for music-today results.
`note`	No
`exact`	No	Strong archive matches (show_search).
`query`	No
`shows`	No	Related playable OffStereo shows.
`title`	No
`events`	No	Dated music-history events (music-today).
`object`	Yes	discovery or show_search.
`recent`	No
`status`	Yes
`webUrl`	No
`actions`	No
`related`	No
`releases`	No	New releases (new_releases mode).
`sections`	No
`allowSave`	No
`allowBuild`	No
`archiveUrl`	No
`playableOnly`	No
`matchedGenres`	No
`requestedGenres`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 22, 2026

changedInput schema / properties / type / description

Previous value: -"Discovery mode. search aliases archive; dated music-history requests use music_today."New value: +"Discovery mode. trending returns the pre-built fresh surface: the Friday Rundown, this week's records and today's anniversary, chart and news stories, every one already built and playable; search aliases archive; dated music-history requests use music_today."

changedInput schema / properties / type / enum

Previous value: -[
-  "new_releases",
-  "archive",
-  "search",
-  "popular"
-]New value: +[
+  "new_releases",
+  "trending",
+  "archive",
+  "search",
+  "popular"
+]

First observedSep 10, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description adds useful workflow context such as single-call cardinality, no-padding relevance behavior, playableOnly scoping, and result-card playback behavior. It does not cover every possible operational detail, but it meaningfully reduces ambiguity beyond the annotations.

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 front-loaded with the tool's purpose and then proceeds through usage constraints, but it is fairly dense and repeats the no-padding idea across multiple sentences. Most sentences earn their place, though the density could be trimmed slightly.

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?

Given the tool's complexity, multiple modes, and the presence of an output schema, the description supplies the key usage, routing, and result-card context an agent needs. It does not need to restate every schema field because the schema and output schema already provide structured detail.

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

Parameters4/5

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

Schema coverage is 100%, so parameter meanings are already documented, but the description adds semantic guidance for genres, query wording, and the music_today exclusion. It does not explicitly explain every parameter such as limit or perGenreLimit, but its added guidance is substantive rather than repetitive.

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 states a specific verb-resource pairing and enumerates the discovery modes: genre-aware new releases, public-archive matches, and popular OffStereo shows. It also distinguishes discover from music_today for dated music-history requests, so an agent can route correctly among siblings.

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

Usage Guidelines5/5

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

It gives explicit invocation rules: call exactly once per listener request, aggregate all positive genres into one array, use [] when no genres were requested, and avoid one call per genre. It also names the alternative for dated history requests (music_today) and clarifies when a separate song card is appropriate.

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

All OffStereo 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?