Skip to main content
Glama
Sign In
mcp-divoom-lan

mcp-divoom-lan

Official
by DivoomDevelop
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

watchface_protocol_quick_reference

Retrieve concise watchface protocol constraints from the Divoom guide and skill before authoring, including model-specific resolution and capability rules for TimesFrame and AstroToo.

Instructions

Return concise operational constraints extracted from the public guide and skill. For AstroToo, first query hardware/capabilities; use the 480x480 AstroToo resources. Legacy 800x1280 examples and typography apply only to TimesFrame.

Input Schema

NameRequiredDescriptionDefault
modelNoFor offline authoring only. A connected target's hardware determines its model.
targetNoOptional per-call target override. If omitted, environment variables are used.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.0
    • addedInput schema / properties / model
      Added value: +{
+  "description": "For offline authoring only. A connected target's hardware determines its model.",
+  "enum": [
+    "timesframe",
+    "astrotoo"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / target
      Added value: +{
+  "additionalProperties": false,
+  "description": "Optional per-call target override. If omitted, environment variables are used.",
+  "properties": {
+    "hardware": {
+      "description": "Explicit PIXOO64 90/92/96 or TimeGate 400/402 profile for direct LAN control. Must match the actual device; this is not a firmware version.",
+      "enum": [
+        90,
+        92,
+        96,
+        400,
+        402
+      ],
+      "type": "integer"
+    },
+    "host": {
+      "description": "Device LAN IP. Example: 192.168.1.120",
+      "type": "string"
+    },
+    "model": {
+      "default": "auto",
+      "description": "PIXOO64/TimeGate use discovery Hardware or target.hardware; TimesFrame/AstroToo query Hardware on the device.",
+      "enum": [
+        "auto",
+        "timesframe",
+        "astrotoo",
+        "pixoo64",
+        "timegate"
+      ],
+      "type": "string"
+    },
+    "port": {
+      "description": "Optional HTTP port override. Defaults to 80 for PIXOO64 90/92 and TimeGate 400, otherwise 9000.",
+      "type": "integer"
+    },
+    "timeoutMs": {
+      "default": 45000,
+      "description": "HTTP timeout in milliseconds.",
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}
  2. First observedv0.1.6

TDQS

B3.4/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 full burden. 'Return' implies a read-only lookup and the model-applicability notes add real context, but the description never describes what the returned constraints actually contain or their format, which is a meaningful gap for a no-annotation, no-output-schema tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the purpose and followed by model-specific caveats. Efficient, though the second sentence packs two distinct conditional rules that could be clearer.

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

Completeness3/5

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

For a 2-param reference tool with full schema coverage and no output schema, the description covers purpose and model scoping but is vague about the actual content and structure of the returned constraints, leaving the agent unsure what it will receive.

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 100%, with the model enum and nested target object fully documented in the schema. The description's mentions of AstroToo/TimesFrame loosely map to the model parameter but add little syntax or format detail beyond what the schema already provides, so the baseline 3 applies.

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?

States a specific verb and resource: returns 'concise operational constraints extracted from the public guide and skill.' An agent can grasp this is a reference-lookup tool. However it doesn't clearly differentiate itself from sibling reference tools like watchface_command_list or pixoo64_command_list.

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?

Provides model-conditional guidance ('For AstroToo, first query hardware/capabilities; use the 480x480 AstroToo resources' and legacy constraints apply only to TimesFrame), which is useful context. But it never states explicitly when to call this tool versus the sibling command_list/reference tools, leaving selection to inference.

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