CWI Discovery Engine

Get Release Info

get_release

Read-onlyIdempotent

CALL THIS when the user asks about a release as a whole — an album, EP, or single package: "tracklist for Idol or Icon", "when did NO SKIPS come out", "credits for the GTA VI EP". Returns the release fact packet: tracklist, date, credits, background. Use get_track instead when the user asks about one specific song.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_release"
  }
}

Input Schema

Name	Required	Description	Default
`id`	No	Release id, e.g. "cyberpunk-2027". Omit for the latest release.

Output Schema

Name	Required	Description
`id`	Yes
`found`	Yes
`packet`	No	Fact packet: facts list of {claim, evidence{source, observed}, tier}.
`_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.
`known_releases`	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_release response: release fact packet (claims with evidence tiers) or not-found.",
+  "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"
+    },
+    "found": {
+      "type": "boolean"
+    },
+    "id": {
+      "type": "string"
+    },
+    "known_releases": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "packet": {
+      "additionalProperties": true,
+      "description": "Fact packet: facts list of {claim, evidence{source, observed}, tier}.",
+      "type": "object"
+    },
+    "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": [
+    "id",
+    "found"
+  ],
+  "type": "object"
+}

AddedOct 6, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the description only needs to add context. It does: it names the return payload ('the release fact packet: tracklist, date, credits, background'), which tells the agent what it will get back before calling. It stops short of deeper traits like pagination or completeness guarantees.

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, the trigger front-loaded ahead of the return description and the sibling routing. The quoted user-phrasing examples earn their place by anchoring pattern matching; nothing is redundant.

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, return values need not be enumerated in prose, and annotations carry the safety profile. Combined with the 100%-covered single parameter and explicit sibling routing, the description gives the agent everything needed to select and invoke the 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?

The single parameter has 100% schema description coverage ('Release id, e.g. "cyberpunk-2027". Omit for the latest release.'), so the schema already carries the semantics. The description adds no id format or defaulting detail, making the baseline 3 correct.

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 immediately scopes it ('a release as a whole — an album, EP, or single package'), with concrete examples that an agent can match against user phrasing. It explicitly contrasts with get_track, so the agent can distinguish it from the nearest sibling 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?

Front-loads the trigger ('CALL THIS when the user asks about a release as a whole') and names the exclusion condition plus the alternative tool ('Use get_track instead when the user asks about one specific song'). Both when-to-use and when-not-to-use are explicit.

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.