Skip to main content
Glama
wave-av

WAVE MCP Server

Official
by wave-av
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wave_control_camera

Send a camera control command to adjust iris, focus, zoom, gain, white balance, shutter, audio levels, presets, or recording state. Specify the command and required fields to apply the change.

Instructions

Send a control command to a managed camera (POST /v1/cameras/{id}/control). command selects the variant; supply only the fields that variant needs: set_iris/set_focus/set_zoom/set_gain use value; set_white_balance uses temperature+tint; set_shutter uses angle; set_audio_level uses channel+level; recall_preset uses preset_id; save_preset uses name+slot; start_recording/stop_recording/start_prerecord/autofocus_trigger take no extra fields

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoPreset name for save_preset
slotNoPreset slot (1-20) for save_preset
tintNoTint for set_white_balance
angleNoShutter angle for set_shutter
levelNoAudio level for set_audio_level
valueNoNumeric value for set_iris/set_focus/set_zoom/set_gain
channelNoAudio channel for set_audio_level
commandYesThe camera command variant
camera_idYesThe camera ID
preset_idNoPreset ID for recall_preset
temperatureNoColor temperature for set_white_balance

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed19 schema fields changedv0.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / action
      Removed value: -{
-  "description": "Camera control action",
-  "enum": [
-    "move",
-    "zoom",
-    "focus",
-    "recall_preset",
-    "store_preset"
-  ],
-  "type": "string"
-}
    • addedInput schema / properties / angle
      Added value: +{
+  "description": "Shutter angle for set_shutter",
+  "type": "number"
+}
    • addedInput schema / properties / camera_id / pattern
      Added value: +"^([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)$"
    • addedInput schema / properties / channel
      Added value: +{
+  "description": "Audio channel for set_audio_level",
+  "type": "number"
+}
    • addedInput schema / properties / command
      Added value: +{
+  "description": "The camera command variant",
+  "enum": [
+    "set_iris",
+    "set_focus",
+    "set_zoom",
+    "set_white_balance",
+    "set_gain",
+    "set_shutter",
+    "start_recording",
+    "stop_recording",
+    "start_prerecord",
+    "autofocus_trigger",
+    "set_audio_level",
+    "recall_preset",
+    "save_preset"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / level
      Added value: +{
+  "description": "Audio level for set_audio_level",
+  "type": "number"
+}
    • addedInput schema / properties / name
      Added value: +{
+  "description": "Preset name for save_preset",
+  "minLength": 1,
+  "type": "string"
+}
    • removedInput schema / properties / pan
      Removed value: -{
-  "description": "Pan speed (-1 to 1)",
-  "maximum": 1,
-  "minimum": -1,
-  "type": "number"
-}
    • changedInput schema / properties / preset_id / description
      Previous value: -"Preset ID for recall/store"New value: +"Preset ID for recall_preset"
    • addedInput schema / properties / preset_id / format
      Added value: +"uuid"
    • addedInput schema / properties / preset_id / pattern
      Added value: +"^([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)$"
    • addedInput schema / properties / slot
      Added value: +{
+  "description": "Preset slot (1-20) for save_preset",
+  "maximum": 20,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / temperature
      Added value: +{
+  "description": "Color temperature for set_white_balance",
+  "type": "number"
+}
    • removedInput schema / properties / tilt
      Removed value: -{
-  "description": "Tilt speed (-1 to 1)",
-  "maximum": 1,
-  "minimum": -1,
-  "type": "number"
-}
    • addedInput schema / properties / tint
      Added value: +{
+  "description": "Tint for set_white_balance",
+  "type": "number"
+}
    • addedInput schema / properties / value
      Added value: +{
+  "description": "Numeric value for set_iris/set_focus/set_zoom/set_gain",
+  "type": "number"
+}
    • removedInput schema / properties / zoom
      Removed value: -{
-  "description": "Zoom speed (-1 to 1)",
-  "maximum": 1,
-  "minimum": -1,
-  "type": "number"
-}
    • changedInput schema / required
      Previous value: -[
-  "camera_id",
-  "action"
-]New value: +[
+  "camera_id",
+  "command"
+]
  2. First observedv0.1.5

TDQS

A3.9/5.0
Behavior3/5

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

There are no annotations, so the description carries the transparency burden. It adds useful behavioral detail about which fields each command variant requires and which commands need no extra fields. However, it does not disclose side effects, permissions, camera-managed prerequisites, or response/error behavior, making it adequate but not rich.

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 one dense, well-organized sentence that front-loads the purpose and endpoint, then uses semicolon-separated mappings for all command variants. Every piece of content contributes directly to correct invocation, with no filler or repetition.

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?

Given the complexity of 11 parameters and 13 command variants, the description covers the essential combinatorial logic completely, including which commands require no extra fields. It omits return-value and error details, but those are not necessary for an agent to select and invoke the command correctly.

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 description coverage is 100%, so the baseline is 3. The description adds a critical layer by mapping each `command` enum value to its required parameters, e.g., set_white_balance uses temperature+tint and set_shutter uses angle. This materially reduces ambiguity for the agent, though units and value ranges are left to the schema.

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 identifies the action ('Send a control command to a managed camera'), gives the endpoint, and enumerates all supported command variants. It does not explicitly differentiate from the only other camera-related sibling, wave_switch_camera, but the purpose is specific enough to avoid major confusion.

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 description provides clear context for when to use this tool: when sending control commands to managed cameras. It also gives practical guidance on selecting the correct parameter subset per command variant. It does not mention alternatives or exclusions, but the boundary against stream/design/production tools is reasonably evident.

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