Skip to main content
Glama
DivoomDevelop

mcp-divoom-lan

Official

watchface_upload_file

Upload a watchface file to a Divoom LAN device by providing the file path and metadata.

Instructions

POST /upload with multipart. First JSON part is caller-provided metadata (product-specific Command). 传输文件打包要求:固件在 divoom_http_server_upload_get_file_info 中要求每个文件段必须有 Content-Length,而浏览器 FormData 通常只使用 boundary 分隔、不包含每段 Content-Length。正在实现固件在无 Content-Length 时用 boundary 终止解析,并修复 JSON 段之后定位文件数据的指针计算;编辑器侧改为手动构造带 Content-Length 的 multipart 以提高兼容性。This server builds multipart with per-part Content-Length.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNoOptional per-call target override. If omitted, environment variables are used.
filePathYes
metadataYes
filePartNameNoSecond multipart part name. Default is current UTC ms timestamp.
fileNameNoFilename in multipart header. Defaults to basename(filePath).
Behavior2/5

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

No annotations are present, so the description must carry the full burden. It mentions multipart handling and firmware compatibility but fails to disclose important traits like authentication requirements, error behavior, or side effects of uploading.

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

Conciseness2/5

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

The description is long and includes a large Chinese block that is irrelevant to an AI agent trying to use the tool. It lacks conciseness and buries the key action in technical details.

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?

Given the tool has 5 parameters (including nested objects) and no output schema, the description is incomplete. It does not explain return values, error cases, or how to construct the metadata parameter, leaving significant gaps for an agent.

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 description coverage is 60%, so the baseline is 3. The description adds minimal value beyond the schema, only hinting that metadata is a 'product-specific Command' but not explaining the structure or constraints of filePath, fileName, etc.

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

Purpose2/5

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

The description is overly technical, starting with 'POST /upload with multipart' and includes a large Chinese block about firmware internals, but does not clearly state that the tool uploads a file to a device. An AI agent would struggle to infer the core purpose.

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?

No explicit guidance on when to use this tool versus siblings like watchface_patch_local or watchface_replace_dial_bg_file. No prerequisites or conditions for use are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DivoomDevelop/mcp-divoom-lan'

If you have feedback or need assistance with the MCP directory API, please join our Discord server