pixoo-mcp-server

Overview Schema Source Related Servers Discussions Admin

pixoo_control_device

pixoo_control_device

Idempotent

Read or change Pixoo LED brightness, screen power, channel, or clock face. No parameters reads current state; supplied parameters apply changes first.

Instructions

Read or change device state: brightness (0–100), screen on/off, channel, or clock face. Call with no params to read current state only. Supply any params to apply changes before reading back state. Use pixoo_discover_devices first if PIXOO_IP is not yet configured.

Input Schema

TableJSON Schema

Name	Required	Description
`screen`	No	Turn the display screen on or off.
`channel`	No	Switch to a channel: faces, cloud, visualizer, or custom.
`brightness`	No	Set display brightness (0–100).
`clockFaceId`	No	Select a clock face by ID (channel must be faces).

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`notice`	No	Requested settings that failed, each with its failure kind and message (e.g. "brightness:80 failed (network): …"), joined by "; ". Absent when every requested setting applied.
`applied`	No	Settings successfully applied in this call (e.g. "brightness:80", "screen:on"). Empty when called with no params or all changes failed. A requested setting that failed is absent here and reported in a notice instead.
`channel`	No	Current channel name (faces, cloud, visualizer, or custom). Absent when device is unreachable.
`clockId`	No	Current clock face ID (faces channel only). Absent on other channels or when device is unreachable.
`screenOn`	No	True if the screen is on. Absent when device is unreachable.
`reachable`	No	True if device responded to the status read.
`brightness`	No	Current brightness level (0–100). Absent when device is unreachable.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.2.0Sep 25, 2026

addedOutput schema / properties / notice

Added value: +{
+  "description": "Requested settings that failed, each with its failure kind and message (e.g. \"brightness:80 failed (network): …\"), joined by \"; \". Absent when every requested setting applied.",
+  "type": "string"
+}

Changed2 schema fields changedv1.1.3Sep 22, 2026

changedOutput schema / properties / error / properties / data / properties / reason / description

Previous value: -"Machine-readable failure mode. Declared by this tool: `device_unreachable`: Device is not reachable. `device_rejected`: Device rejected the command. `no_device_configured`: PIXOO_IP is not set. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `no_device_configured`: PIXOO_IP is not set. Other values are possible when a failure originates below the handler."

changedOutput schema / properties / error / properties / data / properties / reason / examples

Previous value: -[
-  "device_unreachable",
-  "device_rejected",
-  "no_device_configured"
-]New value: +[
+  "no_device_configured"
+]

Changed6 schema fields changedv1.1.1Aug 24, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "reachable",
+      "applied"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `device_unreachable`: Device is not reachable. `device_rejected`: Device rejected the command. `no_device_configured`: PIXOO_IP is not set. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "device_unreachable",
+            "device_rejected",
+            "no_device_configured"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "reachable",
-  "applied"
-]

First observedv1.0.0Jun 17, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already establish idempotent and non-destructive behavior, so the description only needs to add extra context. It does so by explaining the read-only vs. apply-then-read behavior, which is not visible in the schema or annotations. It stops short of describing edge cases like invalid parameter combinations, but the output schema and annotations cover the core safety profile.

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 sentences, each earning its place: the first states scope, the second defines read vs. change behavior, the third gives the prerequisite. Information is front-loaded and there is no filler or repetition of schema content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema, annotations, and full schema parameter descriptions, the description covers everything an agent needs to invoke this tool correctly: what it operates on, how to read vs. change, and when to call the discovery tool first. No critical operational gap remains.

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 coverage is 100%, so the baseline is 3. The description adds value beyond the schema by defining the no-params read mode and the supply-params-to-apply mode, which is essential for using the parameters correctly. It also reinforces the brightness range and channel/clock face relationship without merely repeating schema text.

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?

Description states a specific verb ('Read or change') and resource ('device state') and enumerates the exact aspects affected: brightness, screen on/off, channel, clock face. This clearly differentiates it from sibling tools like pixoo_display_text or pixoo_push_image, which handle content rather than device state.

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

Usage Guidelines5/5

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

Provides explicit usage modes: call with no params to read state, supply params to apply changes and read back. It also names the prerequisite alternative, pixoo_discover_devices, for when PIXOO_IP is not configured, giving clear routing guidance.

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

Deploy Server