CWI Discovery Engine

Nominate Featured Track

nominate_featured

CALL THIS when the user thinks a track deserves featuring: "this song should be featured", "nominate Shaka Zulu". Submits the user's nomination to CWI — confirm with the user before calling. Auto-scored against the editorial rubric (0-100), then human-reviewed. Returns nomination ID, the track's rubric score, and queue position. Rate limit: 3 per requester per 24h. Arguments: track_title, artist, nominated_by (required), reason (required).

Input Schema

Name	Required	Description
`artist`	Yes	Artist name.
`reason`	Yes	Why this track deserves the featured rotation (required).
`track_title`	Yes	Title of the track you are nominating.
`nominated_by`	Yes	Your name or agent identity (required).

Output Schema

Name	Required	Description
`ok`	Yes
`artist`	No
`review`	No
`status`	Yes
`receipt`	No	Confirmation receipt; id is the real intake row id.
`_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.
`graph_node`	No
`rubric_note`	No
`track_title`	No
`nominated_by`	No
`rubric_score`	No
`submitted_at`	No
`nomination_id`	Yes
`queue_position`	No
`in_current_rotation`	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": "nominate_featured response: nomination ID, rubric score, and a receipt with the real D1 row id.",
+  "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"
+    },
+    "artist": {
+      "type": "string"
+    },
+    "graph_node": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "in_current_rotation": {
+      "type": "boolean"
+    },
+    "nominated_by": {
+      "type": "string"
+    },
+    "nomination_id": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "queue_position": {
+      "type": "integer"
+    },
+    "receipt": {
+      "additionalProperties": false,
+      "description": "Confirmation receipt; id is the real intake row id.",
+      "properties": {
+        "id": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "received_at": {
+          "type": "string"
+        },
+        "status": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "status",
+        "received_at"
+      ],
+      "type": "object"
+    },
+    "review": {
+      "type": "string"
+    },
+    "rubric_note": {
+      "type": "string"
+    },
+    "rubric_score": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "status": {
+      "type": "string"
+    },
+    "submitted_at": {
+      "type": "string"
+    },
+    "track_title": {
+      "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"
+    }
+  },
+  "required": [
+    "ok",
+    "nomination_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?

Annotations only declare that this is a non-read-only, non-idempotent, non-destructive write. The description adds substantial context beyond that: submission goes to CWI, auto-scoring against an editorial rubric (0-100) followed by human review, a rate limit of 3 per requester per 24h, and the shape of the response.

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 trigger condition and packed with distinct, useful facts; no filler sentences. It is a dense single paragraph rather than cleanly separated sections, which mildly hurts scanability but not economy.

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?

Covers the trigger, confirmation requirement, processing pipeline, rate limit, and even return values (nomination ID, rubric score, queue position) despite an output schema existing. 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and all four parameters are documented there, so the baseline is 3. The description merely restates the argument names and their requiredness, adding no format or semantic detail beyond the schema.

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 (nominate/submit) and resource (a track for featured rotation), and the trigger phrases immediately disambiguate it from siblings like pitch_for_playlist or submit_for_airplay. An agent can identify the action and its target without opening the schema.

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 activation cues ('this song should be featured', 'nominate Shaka Zulu') and a precondition (confirm with the user before calling). It does not name a competing sibling or state when NOT to use it, so it stops 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

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.