CWI Discovery Engine

Find Tracks for a Brief

find_tracks_for_brief

Read-onlyIdempotent

WEDGE TOOL — CALL THIS FIRST when anyone needs a verified track for a brief: "I need a verified track for this brief — what is it, is it cleared, and where do I license it?" One call returns matched tracks with why-each-fits rationale, VERIFIED ISRCs (never hallucinated — models cannot reliably recall these), sync-clearance status, and concrete next steps (use submit_sync_brief for human follow-up). Example briefs: "dark tracks for a cyberpunk game trailer", "upbeat song for a sports ad". A match is NOT a license grant — clearance still requires a brief. Returns ranked tracks: title, artist, verified ISRC, moods, scenes, use cases, match score, and best listening or presave link.

Input Schema

Name	Required	Description
`brief`	Yes	Natural-language music brief, e.g. "tense instrumental for a heist scene". Truncated at 500 characters.
`limit`	No	Max tracks to return, 1-5 (default 3).
`explicit`	No	true = explicit only, false = non-explicit only. Omit for all.

Output Schema

Name	Required	Description
`brief`	Yes
`count`	Yes
`tokens`	No
`tracks`	Yes
`_session`	No	Chain session: pass _session.session_token back in the next call to continue the chain.
`try_next`	No	Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload.
`next_steps`	Yes	Concrete actions: submit_sync_brief with the brief, contact email, license terms URL.
`generated_at`	No
`clearance_summary`	Yes	Plain-language clearance status for the matched tracks: who controls master+publishing, one-signature terms, PRO.
`licensing_disclaimer`	Yes	States that a match is not a license grant.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026

addedOutput schema / properties / tracks / items / properties / best_link

Added value: +{
+  "additionalProperties": true,
+  "description": "Best available listen link: presave (unreleased) > Spotify > Apple Music, with kind label.",
+  "type": [
+    "object",
+    "null"
+  ]
+}

AddedOct 15, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations cover the read-only/idempotent safety profile, and the description adds material context beyond them: ISRCs are verified rather than hallucinated, and a match is explicitly NOT a license grant so clearance still requires a brief. It also discloses the handoff path to submit_sync_brief.

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 the wedge/call-first cue and dense with useful content, though the block is fairly long and carries some promotional phrasing ('WEDGE TOOL', 'never hallucinated') that could be trimmed. Every sentence still conveys usable information.

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 an output schema present and annotations covering the safety profile, the description still supplies the non-obvious constraints (verification guarantee, non-license caveat, follow-up tool). Nothing needed to select or call it correctly is missing.

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 coverage is 100%, so the schema already documents brief, limit, and explicit fully. The description adds example brief phrasing but no format or semantics beyond what the schema provides, so baseline 3 applies.

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+resource and its scope ('verified track for a brief'), and explicitly names the outcome set (matched tracks, rationale, ISRCs, clearance, next steps). It distinguishes itself from submit_sync_brief, which it identifies as the human-follow-up path.

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?

'CALL THIS FIRST' plus a quoted user intent gives an unambiguous trigger, and it names submit_sync_brief as the alternative for human follow-up. It also supplies concrete example briefs so the agent knows the input shape.

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

All CWI Discovery Engine tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.