Skip to main content
Glama
wave-av

WAVE MCP Server

Official
by wave-av
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wave_show_graphic

Show or hide a graphics overlay on a live production using production and overlay IDs to control its visibility.

Instructions

Show or hide a graphics overlay in a production (POST /v1/productions/{id}/overlay)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
visibleYesWhether the overlay should be visible
overlay_idYesThe overlay ID (1-100 chars)
production_idYesThe production ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / action
      Removed value: -{
-  "description": "Action to perform",
-  "enum": [
-    "show",
-    "hide",
-    "update"
-  ],
-  "type": "string"
-}
    • removedInput schema / properties / data
      Removed value: -{
-  "additionalProperties": {},
-  "description": "Data bindings for the graphic template",
-  "type": "object"
-}
    • removedInput schema / properties / graphic_id
      Removed value: -{
-  "description": "The graphic template ID",
-  "type": "string"
-}
    • addedInput schema / properties / overlay_id
      Added value: +{
+  "description": "The overlay ID (1-100 chars)",
+  "maxLength": 100,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / production_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 / visible
      Added value: +{
+  "description": "Whether the overlay should be visible",
+  "type": "boolean"
+}
    • changedInput schema / required
      Previous value: -[
-  "production_id",
-  "graphic_id",
-  "action"
-]New value: +[
+  "production_id",
+  "overlay_id",
+  "visible"
+]
  2. First observedv0.1.5

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does disclose that this is a state-changing operation (show/hide) and includes the POST method, which is useful. However, it does not mention side effects, prerequisites, idempotency, or error behavior, which would be valuable for a mutation tool.

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 sentence that front-loads the core action and context, and includes the endpoint without any filler. Every part earns its place.

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 simple three-parameter mutation tool with complete schema descriptions, the description is largely sufficient to invoke the tool correctly. It could optionally mention the response or prerequisites, but the absence of an output schema and the simplicity of the operation make those gaps minor.

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?

The input schema already covers 100% of parameters with meaningful descriptions, so the baseline is 3. The description adds no additional parameter-level detail beyond what the schema provides, other than implied linkage through the endpoint path.

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 clearly states the action ('Show or hide'), the resource ('graphics overlay'), and the context ('in a production'), and reinforces it with the exact endpoint. This is specific enough to distinguish the tool from siblings focused on design, streaming, camera control, or production management.

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

Usage Guidelines3/5

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

The description implies when to use the tool—whenever overlay visibility needs to be changed—but it does not explicitly state when not to use it or mention alternatives. The context is clear, but there is no explicit routing guidance relative to other 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