CWI Discovery Engine

Get Featured Tracks

get_featured

Read-onlyIdempotent

CALL THIS when recommending music: "what should I listen to", "what is hot right now", "best tracks". Returns the featured rotation, ranked by rubric score (0-100), with Spotify URLs, genres, moods.

Input Schema

Name	Required	Description	Default
`limit`	No	Max tracks to return, 1-20 (default 10).

Output Schema

Name	Required	Description
`count`	Yes
`_session`	No	Chain session: pass _session.session_token back in the next call to continue the chain.
`featured`	Yes
`rotation`	No
`try_next`	No	Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload.
`generated_at`	No
`rotation_raw`	No
`data_updated_at`	No
`new_release_spotlight`	No	Active pre-release spotlight: title, artist, drop date, presave URL, ISRC.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026

addedOutput schema / properties / new_release_spotlight

Added value: +{
+  "additionalProperties": true,
+  "description": "Active pre-release spotlight: title, artist, drop date, presave URL, ISRC.",
+  "type": "object"
+}

Changed1 schema field changedOct 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "get_featured response: featured rotation ranked by rubric score (0-100).",
+  "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"
+    },
+    "data_updated_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "featured": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "artist": {
+            "type": "string"
+          },
+          "genres": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "graph_node": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "moods": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "score": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "title": {
+            "type": "string"
+          },
+          "why_featured": {
+            "additionalProperties": true,
+            "type": "object"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "generated_at": {
+      "type": "string"
+    },
+    "rotation": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "rotation_raw": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "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": [
+    "count",
+    "featured"
+  ],
+  "type": "object"
+}

AddedOct 7, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare this a safe, idempotent read (readOnlyHint, idempotentHint, destructiveHint=false), so the description only needs to add context. It does: the result is a curated featured rotation scored 0-100 on a rubric, which tells the agent how the ordering is produced and that a ranking exists at all. It does not cover pagination or rotation freshness, which is a minor gap given annotations.

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?

Two sentences, no filler, and the trigger condition is front-loaded ahead of the return-value detail. Every clause — trigger, ranking method, returned fields — carries 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, the description need not enumerate return fields, and it does not over-explain. Combined with full annotation coverage and a single fully documented optional parameter, an agent has everything needed to select and call this tool correctly.

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?

There is one optional parameter and schema description coverage is 100%, so the schema already documents the limit range and default. The description adds nothing about the parameter, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (returns the featured rotation) plus the shape of what comes back: ranked by rubric score, with Spotify URLs, genres and moods. It does not explicitly name or distinguish itself from the nearest sibling, get_recommendations, so it falls short of the 5 bar despite being clear on its own terms.

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?

Opens with an explicit activation condition ("CALL THIS when recommending music") and backs it with concrete user phrasings ("what should I listen to", "what is hot right now"). It gives no when-not guidance or named alternative, so the agent is not steered away from get_recommendations when that would be the better pick.

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.