CWI Discovery Engine

Submit Sync Brief

submit_sync_brief

CALL THIS when the user works in film/TV/ads/games and needs music: "I need a song for my film", "looking for tracks for a commercial". Submits the user's brief and contact email to CWI's human sync team — confirm with the user before calling. CWI may follow up by email about this brief. Tracks are NEVER auto-licensed. Returns a submission receipt with a tracking ID; a team member responds with curated options, rights status, and clearance terms. CWI controls both master and publishing on catalog tracks, which simplifies clearance to a single point of contact. Rate limit: 3 per requester per 24h. Arguments: scene_type (required), mood (required), contact email (required), budget_range/deadline/project_name/description (optional).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "scene_type": "<scene_type>",
      "mood": "<mood>",
      "contact": "<contact>"
    },
    "name": "submit_sync_brief"
  }
}

Input Schema

Name	Required	Description
`mood`	Yes	Mood/energy needed (e.g. "dark aggressive", "uplifting anthemic").
`contact`	Yes	Email for follow-up (required).
`deadline`	No	Optional deadline in YYYY-MM-DD format.
`scene_type`	Yes	Type of scene needing music (e.g. "car chase", "romantic montage").
`description`	No	Optional: more detail about the project or scene.
`budget_range`	No	Optional budget range (e.g. "$1k-5k", "$10k+").
`project_name`	No	Optional project/film/show name.

Output Schema

Name	Required	Description
`ok`	Yes
`mood`	No
`status`	Yes
`_session`	No	Chain session: pass _session.session_token back in the next call to continue the chain.
`brief_id`	Yes
`deadline`	No
`try_next`	No	Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload.
`scene_type`	No
`rights_note`	No
`budget_range`	No
`project_name`	No
`submitted_at`	No
`license_block`	No	Markdown licensing summary: rights holders, clearance terms, contact.
`what_happens_next`	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": "submit_sync_brief response: brief ID, review status, and a license_block markdown summary.",
+  "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"
+    },
+    "brief_id": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "budget_range": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "deadline": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "license_block": {
+      "description": "Markdown licensing summary: rights holders, clearance terms, contact.",
+      "type": "string"
+    },
+    "mood": {
+      "type": "string"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "project_name": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "rights_note": {
+      "type": "string"
+    },
+    "scene_type": {
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    },
+    "submitted_at": {
+      "type": "string"
+    },
+    "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"
+    },
+    "what_happens_next": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "brief_id",
+    "status"
+  ],
+  "type": "object"
+}

AddedOct 8, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Discloses behavior beyond the annotations: tracks are never auto-licensed, a human responds with options/rights/clearance terms, CWI follows up by email, and a rate limit of 3 per requester per 24h applies. This is exactly the kind of non-obvious operational and side-effect context the annotations (readOnlyHint=false, idempotentHint=false) only hint at.

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 'CALL THIS when...' trigger, then side effects, receipt/response behavior, clearance context, rate limit, and arguments in a logical order. Dense but nearly every sentence carries distinct value; the master/publishing note is slightly tangential but still useful for clearance reasoning.

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?

Even though an output schema exists (so return values needn't be explained), the description still summarizes the receipt/tracking-ID outcome. With annotations covering the safety profile, the remaining description supplies triggers, side effects, rate limits, and clearance context — fully complete for correct invocation.

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 description coverage is 100%, so the schema already documents all seven parameters with examples. The description's argument list only restates required/optional status and param names, adding no syntax or format detail beyond the schema — the correct baseline 3.

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 and resource — 'Submits the user's brief and contact email to CWI's human sync team' — and grounds it in concrete trigger utterances (film/TV/ads/games needing music). It is readily distinguishable from sibling tools like find_tracks_for_brief or sync_search, which are search tools rather than human-submission tools.

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?

Gives explicit when-to-use context via example user utterances and adds a prerequisite ('confirm with the user before calling'). It doesn't explicitly name the alternative tools (e.g. sync_search, find_tracks_for_brief) or state when not to route here, so it stops just short of full routing guidance.

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

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.