Bridges the disguise Designer API to the Model Context Protocol, letting an AI client control a disguise media server (transport / timeline playback and more) over MCP.
Strong foundation with explicit tool registration, clear descriptions, and proper JSON Schema. All 8 tools have descriptions (avg 156 chars, within 10-1024 baseline). Input schemas present for all tools with typed parameters. Tool annotations correctly applied (readOnlyHint, destructiveHint). Key gaps: parameter descriptions are sparse or missing in generated tools; no output schema documentation; error handling lacks recovery guidance; some parameter constraints not formalized as enums.
Get the latest cached values for the given live-update subscription ids (empty returns all).
List all active disguise Live Update subscriptions and their latest cached values.
Write property values live by subscription id (disguise Live Update 'set'). Changes are undoable and persistent on the Director.
Subscribe to live updates for an object's properties over the disguise Live Update WebSocket. Object uses Designer expression syntax (e.g. "track:track_1"); properties use Python syntax (e.g. "object.lengthInBeats"). Each subscription is also exposed as an MCP resource that pushes change notifications.
Unsubscribe from live updates by subscription id and remove their MCP resources.
Make an arbitrary disguise Designer API request. Provide the HTTP method, the API path (e.g. /api/service/system/osinfo), and an optional JSON body. Use for anything not covered by a dedicated tool.
Generated tools lack parameter descriptions. tools_generated.go registers operations from OpenAPI specs but does not extract or include parameter descriptions in the MCP schema. LLMs cannot infer what 'filter', 'limit', or domain-specific params mean without explicit text.
No output schema documentation. Tools return JSON via jsonResult() but MCP tool definitions do not document the response structure. Agents cannot plan downstream calls or extract fields without trial-and-error.
Error handling lacks recovery guidance. Functions return fmt.Errorf() with minimal context. E.g., 'host is required' in setTarget is good, but most errors (e.g., from d.app.Client().Do()) are opaque. No guidance on retryability or next steps.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 63 | 2026-07-28+ | v2 |
Repoint the bridge at a different disguise server by host and port. Persists to the config file. The disguise Designer API defaults to port 80.
Report which disguise server the bridge is pointed at and whether it is reachable.
Parameter constraints not formalized. 'method' in disguise_raw accepts 'GET or POST (default GET)' as free text, not an enum. 'scheme' in disguise_set_target should be enum ['http', 'https']. Enums prevent hallucinated values.
disguise_live_subscribe and disguise_live_set accept complex nested structures (object arrays with 'id' and 'value' fields) but lack examples or validation rules in descriptions. LLMs may struggle to construct valid payloads.