Skip to main content
Glama

switch_channel

Change which of the creator's connected channels Klyf works with, so every later answer is about that channel. Call this when the user asks to switch, change or use a different channel, to look at another one of their channels, or names one of their own channels and asks about it instead. Takes the channel name as the user says it. Use list_channels first if you do not know what they have connected. Needs no input: it reads their real connected YouTube channel directly. Never ask the creator anything first, not for context, not for a link, not for a title you could look up; call it immediately.

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": {
      "channel": "<channel>"
    },
    "name": "switch_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelYesThe channel to switch to, by name as the creator refers to it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false, destructiveHint=false, openWorldHint=false; the description adds the important context that this is a sticky session-level state change affecting all later answers, and that it reads the real connected channel live. It does not cover failure or ambiguity cases (unknown channel name, multiple similar names), which matters for a name-matching mutation. The line 'Needs no input' sits awkwardly next to a required channel parameter, though it plainly means no extra context beyond the name.

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?

Purpose and triggers are front-loaded, and the guidance is actionable. The closing sentence ('Never ask the creator anything first, not for context, not for a link, not for a title you could look up') is emphatic and partly restates 'Needs no input', so it is slightly longer than necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, non-destructive state-switch tool with no output schema and existing annotations, the description covers purpose, triggers, prerequisite lookup, and call-immediately behavior. Gaps are minor: what happens when the named channel is not found or is ambiguous, and the tension between 'Needs no input' and the required channel argument.

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 coverage is 100%, so the single parameter is already documented, and the description's 'Takes the channel name as the user says it' adds a useful hint that loose, human-spoken names are acceptable rather than IDs or handles. Beyond that it adds no format, alias, or matching-precedence detail. A baseline 3 is right when the schema carries the parameter definition.

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?

The description opens with a specific verb and resource ('Change which of the creator's connected channels Klyf works with') and states the consequence ('every later answer is about that channel'). It also distinguishes itself from list_channels by pointing to it for the lookup case, so an agent can pick correctly 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?

It enumerates concrete trigger phrasings ('switch, change or use a different channel', 'names one of their own channels and asks about it instead') and names the alternative tool with the condition that selects it ('Use list_channels first if you do not know what they have connected'). It even closes off a common failure mode by telling the agent never to ask the creator for context first.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources