CWI Discovery Engine

Get Radio Schedule

get_schedule

Read-onlyIdempotent

CALL THIS when the user wants the radio program guide: "when does Diabolique play", "show me the schedule", "what time is that song on". Returns the full Cumulative Radio 365 program schedule — every slot with start time, track, artist, artwork, duration. The program is a deterministic loop that repeats; times in UTC.

Input Schema

Name	Required	Description	Default
`date`	No	Date for the schedule in YYYY-MM-DD format. Defaults to today (UTC).

Output Schema

Name	Required	Description
`date`	No
`note`	No
`slots`	Yes
`station`	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.
`slot_count`	Yes
`stream_url`	No
`generated_at`	No
`period_seconds`	No
`program_version`	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": "get_schedule response: full Radio 365 rotation — every slot with track, artist, duration, next air time (UTC).",
+  "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"
+    },
+    "date": {
+      "type": "string"
+    },
+    "generated_at": {
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "period_seconds": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "program_version": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "slot_count": {
+      "type": "integer"
+    },
+    "slots": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "station": {
+      "type": "string"
+    },
+    "stream_url": {
+      "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": [
+    "station",
+    "slot_count",
+    "slots"
+  ],
+  "type": "object"
+}

AddedOct 8, 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 (readOnly, idempotent, non-destructive). The description adds genuinely new behavioral context: the schedule is a deterministic repeating loop and all times are UTC, which explains what a returned value means and why the date defaults to today.

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?

Trigger conditions are front-loaded, followed by return contents and then a single clarifying note on the loop and timezone. No sentence is filler and nothing redundant with the schema or annotations is restated.

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 needn't enumerate return values in fine detail, and it still summarizes them. Annotations cover safety, schema covers the parameter, and the description covers invocation context and the deterministic-loop/timezone caveat.

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 date parameter's format and default are already documented, warranting a baseline of 3. The description goes beyond that by explaining the loop is deterministic and repeats, which is the key semantic fact for interpreting the date parameter's effect, plus UTC timezone context.

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 ('Returns the full ... program schedule') and enumerates the returned fields (start time, track, artist, artwork, duration). The embedded trigger phrases ("when does Diabolique play") let an agent distinguish this from siblings like get_up_next or get_radio without opening schemas.

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?

The 'CALL THIS when...' framing plus three concrete user phrasings gives clear activation context. It does not name an alternative tool or state when NOT to use it (e.g., versus get_up_next for immediate next-slot queries), 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.