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

mcp-divoom-lan

Official
by DivoomDevelop
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

watchface_layout_suggest

Returns layout hints for a given display ID by combining catalog metadata with template typography, helping you author ItemList rows or patch fragments within canvas bounds.

Instructions

Return layout hints for a single disp id by combining disp-catalog metadata with aggregated typography (median size/x/y/w/h, frequent colors, alignment mode) mined from bundled marketplace templates. Use before authoring a new ItemList row or ItemPatchList.patch fragment — values are soft guidance, not firmware-enforced. Always clamp boxes to the logical canvas (typically 800×1280). For AstroToo, first query hardware/capabilities; use the 480x480 AstroToo resources. Legacy 800x1280 examples and typography apply only to TimesFrame.

Input Schema

NameRequiredDescriptionDefault
dispYesTarget ItemList[i].disp.
modelNoFor offline authoring only. A connected target's hardware determines its model.
targetNoOptional per-call target override. If omitted, environment variables are used.
canvasWidthNoLogical canvas width for clamp reminders (default 800).
canvasHeightNoLogical canvas height for clamp reminders (default 1280).

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

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses that outputs are soft guidance, not firmware-enforced, and that boxes must be clamped to the logical canvas. It also explains model-dependent behavior and hardware checks. It stops short of describing error behavior or whether results are deterministic, but is substantially more informative than typical.

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?

The description is front-loaded with the core action and then layers usage constraints and model caveats efficiently. It is dense but appropriately sized for a tool with nested target parameters and model-specific behavior. A slightly tighter opening sentence could improve it, but there is very little waste.

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?

The tool has no output schema and five parameters including a nested target object, so the description needs to explain return content and usage context. It does so by naming the typography fields aggregated (median size/x/y/w/h, frequent colors, alignment mode) and by giving model-specific guidance. It is nearly complete, though it does not describe response shape or failure modes in detail.

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 meaningful cross-parameter context beyond the schema: the model affects which resources apply, AstroToo requires a hardware/capabilities query first, and canvas width/height serve clamp reminders. This helps an agent reason about parameter interactions rather than just field meanings.

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 states a specific verb and resource: 'Return layout hints for a single disp id' by combining disp-catalog metadata with aggregated typography from marketplace templates. It clearly distinguishes the tool from siblings like watchface_template_search and watchface_disp_catalog by describing the unique synthesis it performs.

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?

It explicitly says to use this 'before authoring a new ItemList row or ItemPatchList.patch fragment' and clarifies that values are 'soft guidance, not firmware-enforced.' It also gives model-specific routing: for AstroToo, first query hardware/capabilities and use 480x480 resources; legacy 800x1280 examples apply only to TimesFrame.

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