Retrieve full metadata for a specific track from the OnChain Music catalog, including license pricing, available download formats (MP3, WAV, AIF), artist information, BPM, key, mood, and complete license terms. Use this after search_catalog or ai_search to get full details before purchasing a license.
| Name | Required | Description | Default |
|---|---|---|---|
| track_id | Yes | The track ID returned from search_catalog or ai_search results. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full burden. It does indicate a read-only retrieval operation via 'Retrieve' and lists the data categories returned, but it omits operational details such as authentication needs, error behavior, or rate limits. Adequate but not rich.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences: the first states the action and scope, the second provides usage context. No filler or redundancy; front-loaded with the essential purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter retrieval tool with no output schema, the description adequately explains what will be returned (metadata categories, license terms) and when to use it. It could mention return structure or error cases, but the given context is sufficient for this simple tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already fully describes track_id as the ID returned from search_catalog or ai_search, so the description adds little beyond reinforcing that provenance. With 100% schema coverage, the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Retrieve') and resource ('full metadata for a specific track from the OnChain Music catalog'), and enumerates the metadata content. It clearly distinguishes the tool from search_catalog and ai_search by positioning it as the follow-up detail-fetch step.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly states 'Use this after search_catalog or ai_search to get full details before purchasing a license', providing direct when-to-use guidance and naming the alternative discovery tools. This is clear and actionable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.
