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

mcp-divoom-lan

Official
by DivoomDevelop
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

watchface_reset_local_then_cloud

Deletes local system files to reset a Divoom device clock, with an optional cloud refresh to restore synced resources. Use when a device clock is stale or out of sync.

Instructions

Call Device/ResetLocalClockFromServer. This deletes local sys-side files before optional cloud refresh. For AstroToo, first query hardware/capabilities; use the 480x480 AstroToo resources. Legacy 800x1280 examples and typography apply only to TimesFrame.

Input Schema

NameRequiredDescriptionDefault
targetNoOptional per-call target override. If omitted, environment variables are used.
clockIdYes
parentItemIdNo
parentClockIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.0
    • addedInput schema / properties / target / properties / hardware
      Added value: +{
+  "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"
+}
    • addedInput schema / properties / target / properties / model
      Added value: +{
+  "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"
+}
    • removedInput schema / properties / target / properties / port / default
      Removed value: -9000
    • changedInput schema / properties / target / properties / port / description
      Previous value: -"Device HTTP port, commonly 9000."New value: +"Optional HTTP port override. Defaults to 80 for PIXOO64 90/92 and TimeGate 400, otherwise 9000."
  2. First observedv0.1.6

TDQS

C2.6/5.0
Behavior3/5

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

With no annotations, the description carries full burden and does disclose a critical behavior: local sys-side files are deleted. That is a genuine safety-relevant disclosure. But it leaves the 'optional cloud refresh' undefined (no parameter appears to control it), and says nothing about reversibility, permissions, or failure modes.

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

Conciseness3/5

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

Three sentences with no gross padding, and the destructive effect is stated early. But the leading 'Call Device/ResetLocalClockFromServer' restates the tool name, and the TimesFrame typography note is tangential to invocation.

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

Completeness2/5

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

For a nested-schema, no-annotation, no-output-schema mutation tool this is thin. Key identifiers (clockId, parentItemId, parentClockId) are unexplained, the 'optional cloud refresh' trigger is opaque, and there is no return-value or error guidance to compensate for the missing output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 25%: clockId, parentItemId, and parentClockId have no descriptions anywhere. The description mentions hardware querying for AstroToo (loosely mapping to target.model/hardware) but explains none of the three top-level identifiers, which are the parameters an agent actually must supply.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete operation (Device/ResetLocalClockFromServer) and adds the key effect: it deletes local sys-side files before an optional cloud refresh. However, the verb is buried in a protocol path, and nothing distinguishes this from siblings like watchface_get_local or watchface_patch_local. An agent has a rough idea of the action but must infer the 'reset' semantics.

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

Usage Guidelines2/5

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

It provides a device-specific precondition (query hardware/capabilities first for AstroToo, use 480x480 resources) but never says when to choose this tool over alternatives or when not to use it. The destructive reset vs. non-destructive patch/list siblings are not routed at all.

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