opendeck-mcp

Overview Schema Source Related Servers Discussions Admin

add_child

Add a child action inside a Multi Action (runs all children in order) or Toggle Action (cycles one per press). Requires the parent action on a key.

Instructions

Add an action inside a Multi Action (runs all children in order) or Toggle Action (cycles through them, one per press). Put the Multi/Toggle Action on the key with set_key first. Staged only.

Input Schema

TableJSON Schema

Name	Required	Description
`slot`	Yes	Slot holding a Multi/Toggle Action.
`image`	No	Key image: a file path, an http(s) URL, or a data: URL; 'default' restores the action's own.
`title`	No
`action`	Yes	Action uuid or name to add inside it.
`device`	Yes	Device id or name, e.g. 'ulanzi-d200h' (see get_overview).
`profile`	No	Profile id; defaults to the device's selected profile.
`delay_ms`	No	Multi Action only: wait after this child, in ms (default 100).
`position`	No	1-based position; default last.
`settings`	No
`title_style`	No	Title look: show (bool), colour (#RRGGBB), size (int), family (font), style (Regular\|Bold\|Italic\|Bold Italic), alignment (top\|middle\|bottom), underline (bool), stroke_colour, stroke_size, background_colour.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Oct 16, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations cover the safety profile (not read-only, non-destructive, non-idempotent), so the bar is lower, and the description adds genuinely new behavior: 'Staged only' signals changes are not live and require apply_changes, plus the execution semantics of Multi (ordered) vs Toggle (cycled). It stops short of stating the undo/discard counterpart.

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?

Three tight sentences, front-loaded with what the tool does and followed by the prerequisite and staging note. Every clause 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?

An output schema exists so return values need no explanation, and the description covers purpose, prerequisite, and staging for a 10-parameter mutation tool. Coverage is strong, though deeper notes on how staged changes are later applied would round it out.

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 coverage is 80%, so the schema already documents slot, action, device, delay_ms, and position richly, making 3 the baseline. The description adds behavioral meaning to delay_ms via the ordered/cycled distinction but gives no syntax detail beyond what the schema already states.

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?

Specific verb (add) plus resource (an action/child) plus the two container types it targets (Multi Action, Toggle Action), with a clear description of how each container behaves. An agent can distinguish this from siblings like set_key or remove_child without opening a schema.

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?

Provides an explicit prerequisite ('Put the Multi/Toggle Action on the key with set_key first') and the staging constraint ('Staged only'). It does not explicitly name when to prefer this over close siblings like remove_child or set_multi_delays, but the context is clear.

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