CWI Discovery Engine

Search Sync Catalog

sync_search

Read-onlyIdempotent

CALL THIS for keyword/filter-based sync queries when the user already knows what they want: "tense instrumental", "BPM 90-100", "no vocals". This is the precise-query path. Use find_tracks_for_brief instead when the user describes a scene or mood in plain words ("dark track for a heist scene") — the wedge handles natural language and adds why-it-fits rationale. Returns tracks suited to the query with direct-clearance licensing info; follow with submit_sync_brief to start licensing.

Input Schema

Name	Required	Description
`q`	Yes	Sync query, e.g. "club scene" or "dark aggressive". Truncated at 500 characters.
`mood`	No	Mood filter, matched against moods + energy words, e.g. "aggressive".
`bpm_max`	No	Maximum BPM (inclusive).
`bpm_min`	No	Minimum BPM (inclusive).
`explicit`	No	true = explicit only, false = non-explicit only. Omit for all.

Output Schema

Name	Required	Description
`count`	Yes
`query`	Yes
`tokens`	No
`results`	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.
`generated_at`	No
`license_block`	No	Markdown licensing summary for the top hit: ISRC, rights holders, clearance terms, contact.
`filters_applied`	No
`descriptor_provenance`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "sync_search response: scene-matched tracks with rights info, plus a license_block for the top hit.",
+  "properties": {
+    "_session": {
+      "additionalProperties": false,
+      "description": "Chain session: pass _session.session_token back in the next call to continue the chain.",
+      "properties": {
+        "session_token": {
+          "description": "Hex session token; echo it as params._session.session_token to continue.",
+          "type": "string"
+        },
+        "step": {
+          "description": "Hop number in this chain (1 = chain start).",
+          "type": "integer"
+        }
+      },
+      "required": [
+        "session_token",
+        "step"
+      ],
+      "type": "object"
+    },
+    "count": {
+      "type": "integer"
+    },
+    "descriptor_provenance": {
+      "type": "string"
+    },
+    "filters_applied": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "generated_at": {
+      "type": "string"
+    },
+    "license_block": {
+      "description": "Markdown licensing summary for the top hit: ISRC, rights holders, clearance terms, contact.",
+      "type": "string"
+    },
+    "query": {
+      "type": "string"
+    },
+    "results": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "artist": {
+            "type": "string"
+          },
+          "credits": {
+            "type": "string"
+          },
+          "licensing_terms_pointer": {
+            "type": "string"
+          },
+          "moods": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "musical_key": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "rights": {
+            "additionalProperties": true,
+            "type": [
+              "object",
+              "null"
+            ]
+          },
+          "scenes": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "score": {
+            "type": "number"
+          },
+          "title": {
+            "type": "string"
+          },
+          "track_id": {
+            "type": "string"
+          },
+          "use_cases": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "tokens": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "try_next": {
+      "description": "Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload.",
+      "items": {
+        "additionalProperties": false,
+        "description": "Pre-compiled next call: copy `arguments` straight into the next tools/call.",
+        "properties": {
+          "arguments": {
+            "additionalProperties": true,
+            "description": "Ready-to-use arguments, pre-populated from the current response.",
+            "type": "object"
+          },
+          "purpose": {
+            "description": "Why this call is the natural next step.",
+            "type": "string"
+          },
+          "tool": {
+            "description": "Tool to call next.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "tool",
+          "arguments"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "query",
+    "count",
+    "results"
+  ],
+  "type": "object"
+}

Changed4 schema fields changedOct 8, 2026

addedInput schema / properties / bpm_max

Added value: +{
+  "description": "Maximum BPM (inclusive).",
+  "type": "number"
+}

addedInput schema / properties / bpm_min

Added value: +{
+  "description": "Minimum BPM (inclusive).",
+  "type": "number"
+}

addedInput schema / properties / explicit

Added value: +{
+  "description": "true = explicit only, false = non-explicit only. Omit for all.",
+  "type": "boolean"
+}

addedInput schema / properties / mood

Added value: +{
+  "description": "Mood filter, matched against moods + energy words, e.g. \"aggressive\".",
+  "type": "string"
+}

First observedOct 5, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the return nature (direct-clearance licensing info) and the downstream workflow ('follow with submit_sync_brief to start licensing'). It omits pagination or result-count limits, keeping it short of a 5.

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?

Front-loads 'CALL THIS for...' with the core routing signal, then the alternative, then the return/next-step note. Every sentence does routing or workflow work; no filler.

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?

A five-parameter, output-schema-backed search tool is fully served here: when to pick it, which sibling to prefer otherwise, what it returns, and what to call next. Nothing an agent needs to invoke it correctly is missing.

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 is 3. The description nonetheless illustrates how filters combine ('tense instrumental', 'BPM 90-100', 'no vocals'), which maps concretely onto q, bpm, and explicit and helps an agent construct queries. It stops short of enumerating every parameter, so not a 5.

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 (search) and resource (sync catalog) scoped to keyword/filter queries, with concrete query examples. It explicitly distinguishes itself from the sibling find_tracks_for_brief, so an agent can route correctly 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?

Explicit when-to-use ('when the user already knows what they want') plus a named alternative ('Use find_tracks_for_brief instead when the user describes a scene or mood') with the exact condition that selects it. 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 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.