Skip to main content
Glama

OnChain Music

by com.onchainmusic
OverviewDiscussionsAdmin

ai_search

Read-onlyIdempotent

Search the OnChain Music catalog using a plain English description. The API extracts genre, mood, tempo, and other parameters automatically. Best for open-ended requests like "something cinematic and tense for a thriller scene" or "upbeat summer pop for a travel vlog". Returns up to 5 tracks. 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 search_catalog with the parameters in ai_translation.translated_params and page 2.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
phraseYesThe user's request, passed through as close to verbatim as possible. Do not rephrase, expand, or add descriptive words, moods, or synonyms the user did not say; extra words narrow the results. Example: if the user says "I need light pop instrumental songs for a radio ad", send exactly that.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / phrase / description
      Previous value: -"Plain English music description. Examples: \"I need an upbeat indie rock track for a TV commercial\", \"dark ambient music for a horror game\", \"romantic acoustic guitar for a wedding video\"."New value: +"The user's request, passed through as close to verbatim as possible. Do not rephrase, expand, or add descriptive words, moods, or synonyms the user did not say; extra words narrow the results. Example: if the user says \"I need light pop instrumental songs for a radio ad\", send exactly that."
  2. Changed2 schema fields changed
    • removedInput schema / properties / per_page
      Removed value: -{
-  "default": 10,
-  "description": "Number of results to return. Default 10, maximum 50.",
-  "maximum": 50,
-  "minimum": 1,
-  "type": "integer"
-}
    • changedInput schema / properties / phrase / description
      Previous value: -"Plain English music description. Be as descriptive as you like. Examples: \"I need an upbeat indie rock track for a TV commercial\", \"dark ambient music for a horror game\", \"romantic acoustic guitar for a wedding video\"."New value: +"Plain English music description. Examples: \"I need an upbeat indie rock track for a TV commercial\", \"dark ambient music for a horror game\", \"romantic acoustic guitar for a wedding video\"."
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive semantics, but the description adds real behavioral detail beyond them: results are capped at 5, the response carries meta.total and meta.results_url, and the agent is instructed to surface all tracks and the URL to the user. It does not mention auth requirements or rate limits, so not a full 5.

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 purpose, then examples, then result handling, then the escalation path — a logical order with no filler sentences. It runs slightly long with two example phrases and multiple imperative output instructions, but each sentence 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?

With no output schema, the description carries the burden of describing returns and does so precisely: up to 5 tracks, meta.total, meta.results_url, plus ai_translation.translated_params for pagination. An agent has everything needed to call it, present results, and continue paging.

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% and the schema already explains the verbatim-pass-through rule, so the baseline is 3. The description adds mechanism-level meaning by stating that genre, mood, tempo, and other parameters are extracted automatically, which explains why phrasing must not be embellished — a genuine complement to the schema rather than a restatement.

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?

Specific verb (Search) + resource (OnChain Music catalog) + distinguishing mode (plain English description with automatic parameter extraction). It explicitly names the sibling it is not (search_catalog) and explains the division of labor, so an agent can route between them without opening either schema.

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?

Gives concrete when-to-use examples ('something cinematic and tense for a thriller scene'), states the result ceiling (up to 5 tracks), and names the fallback path and exact arguments needed to continue (search_catalog with ai_translation.translated_params and page 2). Nothing is left to inference.

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