Skip to main content
Glama
wave-av

WAVE MCP Server

Official
by wave-av
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wave_switch_camera

Switch the program or preview bus to a different camera index in a multi-camera production. Choose from cut, dissolve, wipe, or fade transitions to change the active camera feed.

Instructions

Switch the program or preview bus to a different camera index in a multi-camera production (POST /v1/productions/{id}/camera)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
busYesWhich bus to switch
transitionNoTransition type (default: cut)
camera_indexYesCamera index to switch to (0-15)
production_idYesThe production ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / bus
      Added value: +{
+  "description": "Which bus to switch",
+  "enum": [
+    "program",
+    "preview"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / camera_index
      Added value: +{
+  "description": "Camera index to switch to (0-15)",
+  "maximum": 15,
+  "minimum": 0,
+  "type": "integer"
+}
    • removedInput schema / properties / duration_ms
      Removed value: -{
-  "description": "Transition duration in ms (default: 0 for cut)",
-  "maximum": 5000,
-  "minimum": 0,
-  "type": "integer"
-}
    • addedInput schema / properties / production_id
      Added value: +{
+  "description": "The production ID",
+  "format": "uuid",
+  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+  "type": "string"
+}
    • removedInput schema / properties / source_id
      Removed value: -{
-  "description": "The source to switch to (e.g., cam_1, screen_share)",
-  "type": "string"
-}
    • removedInput schema / properties / switcher_id
      Removed value: -{
-  "description": "The Cloud Switcher session ID",
-  "format": "uuid",
-  "type": "string"
-}
    • changedInput schema / properties / transition / enum
      Previous value: -[
-  "cut",
-  "mix",
-  "wipe",
-  "dve"
-]New value: +[
+  "cut",
+  "dissolve",
+  "wipe",
+  "fade"
+]
    • changedInput schema / required
      Previous value: -[
-  "switcher_id",
-  "source_id"
-]New value: +[
+  "production_id",
+  "camera_index",
+  "bus"
+]
  2. First observedv0.1.5

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Switch' and gives the endpoint, without describing side effects, immediacy of the switch, permission requirements, reversibility, or how transitions actually behave. This is a significant gap for a state-changing operation.

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?

The description is a single, front-loaded sentence with no filler. The parenthetical endpoint adds orientation, and every part of the text earns its place.

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?

With no annotations, no output schema, and a state-changing operation, the description should provide more context about response behavior, side effects, and when to prefer this over sibling tools. The schema covers parameters well, but the definition as a whole is not contextually complete for an agent to confidently invoke it in all appropriate situations.

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 description coverage is 100%, with each parameter already explained in the input schema. The description adds no additional parameter-level meaning beyond naming the operation, so the baseline of 3 is appropriate.

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?

The description clearly states the action ('Switch'), the resource ('program or preview bus'), and the target ('camera index') in a multi-camera production. It is specific enough to differentiate from broader siblings like wave_control_camera, though it does not explicitly name or contrast siblings.

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?

There is no guidance on when to use this tool versus alternatives such as wave_control_camera, nor any prerequisites or exclusions. The phrase 'in a multi-camera production' implies some context, but does not help an agent decide between this and related camera-control tools.

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

Deploy Server

Other Tools