Skip to main content
Glama

OnChain Music

by com.onchainmusic
OverviewDiscussionsAdmin

search_catalog

Read-onlyIdempotent

Search the OnChain Music catalog of 8,800+ 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

TableJSON 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_typeNoFilter by intended license type. social_media = $5 USDC. all_digital = $35 USDC.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
-}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations cover only the read-safe profile, so the description carries the behavioral burden and does so well: it discloses a hard return cap ('up to 5 tracks per call'), the presence of meta.total and meta.results_url, the pagination mechanism, and a caller obligation to surface those fields. This is meaningful transparency 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?

Front-loaded with what is searched, then filters, then result-handling instructions. Every sentence is functional, though the output-presentation directives (show all tracks, mention meta.total, share meta.results_url) make it slightly long.

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?

With 10 optional params, no output schema, and read-only annotations, the description adequately covers return shape, pagination, and the key search field. It does not explain result ranking/relevance behavior or license semantics beyond the enum labels, but is otherwise sufficient to call correctly.

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 the baseline would be 3, but the description adds routing value by designating the 'description' parameter as the PRIMARY search field for style/mood/energy/use-case words, which the schema alone does not establish relative to keywords.

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?

States a specific verb and resource ('Search the OnChain Music catalog of 8,800+ independently owned, fully cleared songs, plus partner catalogs') and enumerates the filterable facets. It is clearly distinguishable from siblings like get_track (single fetch) and 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 directional guidance: 'Use the description parameter as the primary search field' and 'For more tracks, call again with the next page.' It supplies filtering context but never explicitly contrasts itself with ai_search or names conditions for choosing one over the other.

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