Skip to main content
Glama
wave-av

WAVE MCP Server

Official
by wave-av

wave_switch_camera

Switch the live program output to a different camera or source in a Cloud Switcher session with customizable transitions.

Instructions

Switch the live program output to a different camera/source in a Cloud Switcher session

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
switcher_idYesThe Cloud Switcher session ID
source_idYesThe source to switch to (e.g., cam_1, screen_share)
transitionNoTransition type (default: cut)
duration_msNoTransition duration in ms (default: 0 for cut)

Implementation Reference

  • Handler function for wave_switch_camera that POSTs to /api/v1/switcher/{switcher_id}/control with the switch payload
    async ({ switcher_id, source_id, transition, duration_ms }) => {
      const res = await waveFetch(`/api/v1/switcher/${switcher_id}/control`, {
        method: "POST",
        body: JSON.stringify({
          type: "switch",
          sourceId: source_id,
          transition: transition ?? "cut",
          durationMs: duration_ms ?? 0,
        }),
      });
      if (!res.ok) return errorContent(res.status, res.body);
      return textContent(res.body);
    },
  • Zod schema defining input parameters: switcher_id (UUID), source_id (string), optional transition (enum), optional duration_ms (0-5000)
    {
      switcher_id: z.string().uuid().describe("The Cloud Switcher session ID"),
      source_id: z.string().describe("The source to switch to (e.g., cam_1, screen_share)"),
      transition: z
        .enum(["cut", "mix", "wipe", "dve"])
        .optional()
        .describe("Transition type (default: cut)"),
      duration_ms: z
        .number()
        .int()
        .min(0)
        .max(5000)
        .optional()
        .describe("Transition duration in ms (default: 0 for cut)"),
    },
  • Tool registration using server.tool() in registerProductionTools, exported and called from src/server.ts
    server.tool(
      "wave_switch_camera",
      "Switch the live program output to a different camera/source in a Cloud Switcher session",
      {
        switcher_id: z.string().uuid().describe("The Cloud Switcher session ID"),
        source_id: z.string().describe("The source to switch to (e.g., cam_1, screen_share)"),
        transition: z
          .enum(["cut", "mix", "wipe", "dve"])
          .optional()
          .describe("Transition type (default: cut)"),
        duration_ms: z
          .number()
          .int()
          .min(0)
          .max(5000)
          .optional()
          .describe("Transition duration in ms (default: 0 for cut)"),
      },
      async ({ switcher_id, source_id, transition, duration_ms }) => {
        const res = await waveFetch(`/api/v1/switcher/${switcher_id}/control`, {
          method: "POST",
          body: JSON.stringify({
            type: "switch",
            sourceId: source_id,
            transition: transition ?? "cut",
            durationMs: duration_ms ?? 0,
          }),
        });
        if (!res.ok) return errorContent(res.status, res.body);
        return textContent(res.body);
      },
    );
  • Local waveFetch utility used by the handler to make authenticated HTTP requests to the WAVE API
    async function waveFetch(
      path: string,
      init?: RequestInit,
    ): Promise<{ ok: boolean; status: number; body: string }> {
      const url = `${getBaseUrl()}${path}`;
      const res = await fetch(url, {
        ...init,
        headers: {
          ...getAuthHeaders(),
          ...init?.headers,
        },
      });
      const body = await res.text();
      return { ok: res.ok, status: res.status, body };
    }
Behavior2/5

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

No annotations provided, yet description lacks behavioral details such as whether the session must be active, side effects on recordings, or error conditions. The description is too brief for a mutating action.

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?

Single sentence, no unnecessary words. However, it could be slightly more informative while remaining concise.

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

Completeness2/5

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

Given the absence of annotations and output schema, the description should provide more context about return behavior, error states, and prerequisites. It does not mention that the source_id must be valid or that transitions are optional.

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?

Input schema has 100% description coverage, so baseline is 3. The description adds no extra semantic beyond 'switch to a different camera/source' which is already implied by the tool name and 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?

Description clearly states the action (switch), the resource (live program output), and the context (Cloud Switcher session). It distinguishes from sibling tools like wave_control_camera (camera adjustments) and wave_show_graphic (graphics overlays).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives such as wave_control_camera or wave_show_graphic. No mention of prerequisites or conditions for use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wave-av/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server