Skip to main content
Glama
Sign In

OnChain Music

by com.onchainmusic
OverviewDiscussionsAdmin

search_catalog

Read-onlyIdempotent

Search the OnChain Music catalog of 8,700+ independently owned, fully cleared songs, plus partner catalogs. Filter by genre, tempo, BPM, key, and instrumentation. Use the description parameter as the primary search field for style, mood, energy, and use-case words. Returns up to 5 tracks per call. Show all returned tracks, mention meta.total so the user knows how many matches exist, and always share meta.results_url, which opens every match on onchainmusic.com. For more tracks, call again with the next page.

Input Schema

NameRequiredDescriptionDefault
keyNoMusical key. Examples: C Minor, G Maj, A Minor, F Maj.
pageNoPage number. Use 2, 3, and so on when the user asks for more tracks.
genreNoGenre filter. Examples: Rock, Hip-Hop, Electronica, Orchestral, Jazz, Country, R&B, Pop.
bpm_maxNoMaximum BPM. Use with bpm_min to filter by tempo range.
bpm_minNoMinimum BPM. Use with bpm_max to filter by tempo range.
keywordsNoAdditional keyword search across track titles, artist names, and tags.
subgenreNoSubgenre filter. Examples: Indie, Deep House, Trap, Classical.
descriptionNoPRIMARY search field. Pass style, mood, energy, instrumentation, or use-case words. Each word is searched individually across multiple fields. Example: "epic orchestral trailer" or "upbeat summer pop".
instrumentalNoYes = instrumental only (no vocals). No = has vocals.
license_typeNoShow pricing for one personal (non-commercial) license type: social_media = Personal Social Media ($10 USDC): Personal, non-commercial videos on TikTok, Instagram, YouTube, X, Facebook, and similar platforms. all_digital = Personal All Digital ($35 USDC): Non-commercial use on websites, podcasts, streaming, and online video.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / license_type / description
      Previous value: -"Show pricing for one personal (non-commercial) license type: social_media = Personal Social Media ($1 USDC): Personal, non-commercial videos on TikTok, Instagram, YouTube, X, Facebook, and similar platforms. all_digital = Personal All Digital ($35 USDC): Non-commercial use on websites, podcasts, streaming, and online video."New value: +"Show pricing for one personal (non-commercial) license type: social_media = Personal Social Media ($10 USDC): Personal, non-commercial videos on TikTok, Instagram, YouTube, X, Facebook, and similar platforms. all_digital = Personal All Digital ($35 USDC): Non-commercial use on websites, podcasts, streaming, and online video."
  2. Changed1 schema field changed
    • changedInput schema / properties / license_type / description
      Previous value: -"Show pricing for one personal (non-commercial) license type: social_media = Personal Social Media ($10 USDC): Personal, non-commercial videos on TikTok, Instagram, YouTube, X, Facebook, and similar platforms. all_digital = Personal All Digital ($35 USDC): Non-commercial use on websites, podcasts, streaming, and online video."New value: +"Show pricing for one personal (non-commercial) license type: social_media = Personal Social Media ($1 USDC): Personal, non-commercial videos on TikTok, Instagram, YouTube, X, Facebook, and similar platforms. all_digital = Personal All Digital ($35 USDC): Non-commercial use on websites, podcasts, streaming, and online video."
  3. Changed1 schema field changed
    • changedInput schema / properties / license_type / description
      Previous value: -"Filter by intended license type. social_media = $5 USDC. all_digital = $35 USDC."New value: +"Show pricing for one personal (non-commercial) license type: social_media = Personal Social Media ($10 USDC): Personal, non-commercial videos on TikTok, Instagram, YouTube, X, Facebook, and similar platforms. all_digital = Personal All Digital ($35 USDC): Non-commercial use on websites, podcasts, streaming, and online video."
  4. Changed2 schema fields changed
    • changedInput schema / properties / page / description
      Previous value: -"Page number for pagination. Vary this for different results."New value: +"Page number. Use 2, 3, and so on when the user asks for more tracks."
    • removedInput schema / properties / per_page
      Removed value: -{
-  "default": 20,
-  "description": "Results per page. Default 20, maximum 50.",
-  "maximum": 50,
-  "minimum": 1,
-  "type": "integer"
-}
  5. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive, and closed-world behavior. The description adds useful operational details beyond annotations: 8,700+ track scope, partner catalogs, a 5-track cap per call, pagination behavior, and required handling of meta.total and meta.results_url.

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?

Front-loads the catalog scope and filter dimensions, then covers the primary search field, result cap, pagination, and output-handling instructions. The six sentences are compact and each carries operational value.

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?

For a 10-parameter read-only search tool with no output schema, the description supplies catalog scope, primary query guidance, result cap, pagination instructions, and the important meta fields to surface. Filter-level details are left to the fully documented schema, leaving no critical gap for correct invocation.

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%, and every parameter is documented with examples or enums. The description reinforces that description is the primary search field and page supports pagination, but this largely repeats what the schema already says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Search the OnChain Music catalog of 8,700+ independently owned, fully cleared songs, plus partner catalogs,' and lists filter dimensions. It is clear what the tool does, but it does not explicitly distinguish itself from sibling ai_search.

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?

Gives clear usage context: use the description parameter as the primary search field, filter by genre/tempo/BPM/key/instrumentation, paginate with page, show all tracks, mention meta.total, and share meta.results_url. It does not name alternatives such as ai_search or get_track, or say when not to use this tool.

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

All OnChain Music 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