Skip to main content
Glama
DivoomDevelop

mcp-divoom-lan

Official

watchface_font_catalog

Retrieve a curated font catalog to select font IDs for Divoom watchface elements by type, script, style, or scenario.

Instructions

Return a curated font catalog so agents can pick ItemList[i].font ids deterministically. Each entry includes id, type (1=TTF, 0=image-font), display name, original charset, derived script (digits / digits-extended / latin / cjk), style tags (sans/serif/pixel/digital/handwriting/display/decorative/bold/light/etc), and recommendedFor (scenario names like time_digits / temperature_digits / weather_text / user_text / lunar_text). The response also includes a scenarios map that lists which disp ids each scenario covers and which tags to prefer. For visual style and mood per font id, read MCP resource divoom://font/guide first. Use the optional filters to narrow the result. Always cross-check with watchface_get_fonts_local before committing a font id to a real device, because the on-device font list may be a subset.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoFilter by font type. Default 'all'.
scriptNoFilter by derived script. 'digits' = image fonts whose charset is exactly 0-9.
tagNoMatch a single style tag (e.g., 'pixel', 'digital', 'handwriting', 'sans', 'serif', 'cjk-capable').
scenarioNoFilter to fonts whose `recommendedFor` includes this scenario (see top-level `scenarios` map for the full list).
idsNoReturn only the entries whose id is in this list (useful after watchface_get_fonts_local).
limitNoMax number of font entries to return (default 50, max 200).
idsOnlyNoIf true, return only `[{id, name, type_name, script}]` rows for a compact summary.
includeScenariosNoIf true (default), include the top-level `scenarios` map in the response so the agent can map disp ids → preferred tags.
Behavior4/5

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

No annotations are provided, but the description explains the response structure (entries with fields, scenarios map) and filter effects. It does not mention authentication or error handling, but for a read-only catalog query, it is sufficiently transparent about what the tool returns and how it behaves.

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?

The description is well-structured and front-loaded: first sentence states purpose, then details output, then usage guidance. Every sentence adds necessary value without redundancy. It efficiently conveys all essential information.

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?

Given 8 optional parameters and no output schema, the description is quite complete. It explains the output fields, scenarios map, recommends cross-checking and visual resource. Missing details like default filter values (except limit) and error handling, but overall sufficient for an agent to use the tool appropriately.

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 baseline is 3. The description adds value by explaining how parameters like 'ids' are used after watchface_get_fonts_local, and the 'includeScenarios' parameter affects response structure. It also ties filters to narrowing results.

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 clearly states it returns a curated font catalog for deterministic font ID selection, details the output fields (id, type, name, etc.), and distinguishes from sibling 'watchface_get_fonts_local' by explicitly advising cross-check with that tool.

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 provides explicit when-to-use guidance (pick font IDs), recommends using optional filters, and advises always cross-checking with watchface_get_fonts_local before committing. It also suggests reading MCP resource for visual style.

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