Skip to main content
Glama

OnChain Music

by com.onchainmusic

search_catalog

Search the OnChain Music catalog of 6,000+ independently owned, fully cleared tracks, plus partner catalogs. Filter by genre, mood, tempo, BPM, key, and instrumentation. All results are available for immediate licensing with USDC on Base. Use the description parameter as your primary search field — pass style, mood, energy, and use-case words. Returns track IDs, metadata, license pricing, and a results_url in meta that links to a preview page where users can listen to tracks before licensing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoMusical key. Examples: C Minor, G Maj, A Minor, F Maj.
pageNoPage number for pagination. Vary this for different results.
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.
per_pageNoResults per page. Default 20, maximum 50.
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.

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the transparency burden. It discloses that results are immediately licensable with USDC on Base, and that the response includes a results_url for previewing tracks. It does not mention rate limits or side effects, but as a read-only search, the description is reasonably transparent. Minor imprecision: 'filter by mood' but no direct mood parameter.

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 four sentences, front-loaded with the core purpose, then filters, licensing, and return details. Every sentence provides actionable information with no fluff.

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 11 parameters and no output schema, the description covers the tool's scope, filterable attributes, licensing requirement, and return fields including a preview URL. It is complete for a search tool, as pagination details are already in the schema.

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?

The input schema already provides detailed descriptions for all 11 parameters (100% coverage), including examples for the 'description' field. The main description adds a highlight about the 'description' field being primary but does not add substantial new semantic meaning beyond the schema.

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 uses the specific verb 'Search' with the resource 'OnChain Music catalog', and clearly distinguishes it from sibling tools like get_track by focusing on discovery and licensing. It also lists filter dimensions (genre, BPM, key, etc.).

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 for use: finding licensable tracks with USDC, and explicitly directs users to use the 'description' parameter as the primary search field. However, it does not explicitly state when not to use this tool or mention alternatives like ai_search.

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
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

A4.1/5.0
Disambiguation3/5

ai_search and search_catalog both search the OnChain Music catalog using natural language descriptions, making their boundaries unclear despite the descriptions. The other tools (get_track, calculate_royalty_split, get_genre_conventions, get_loudness_standards) are clearly distinct.

Naming Consistency4/5

Most tools follow a clear verb_noun snake_case pattern (calculate_royalty_split, get_genre_conventions, get_loudness_standards, get_track, search_catalog). ai_search deviates from this pattern by using a noun prefix instead of a verb, but the convention is otherwise consistent.

Tool Count5/5

With 6 tools, the server is well-scoped for its purpose: catalog searching, track retrieval, and music business utilities. Each tool contributes a distinct function without unnecessary bloat.

Completeness4/5

The tool set covers catalog search, track metadata retrieval, royalty calculation, genre conventions, and loudness standards. A direct licensing/purchase tool is absent, but the search results include a results_url for external licensing, so the core workflow is supported. Minor gaps like listing all genres or artists are easily worked around via search.

Resources