Skip to main content
Glama
Jelloeater

ulanzi-mcp

show_custom_app

Create or update a custom app on a Ulanzi smart clock, specifying text, colors, icon, duration, and display effects.

Instructions

Create or update a custom app on the clock.

Args: app_name: Unique name for this custom app text: Text to display duration: How long to show in seconds (default: 5) repeat: How many times to repeat scrolling (-1 = infinite, default) color: Text color as hex string or RGB array background: Background color icon: Icon name to display rainbow: Show text in rainbow colors (default: False) effect: Background effect name save: Save to flash memory (default: False) clock_index: Optional index of clock to target (0-based). Defaults to first clock.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_nameYes
textNo
durationNo
repeatNo
colorNo
backgroundNo
iconNo
rainbowNo
effectNo
saveNo
clock_indexNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

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. It mentions 'Create or update' but does not specify if updating replaces or merges, nor does it discuss persistence, permissions, or side effects of the 'save' parameter. Some behavioral details are missing.

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 well-structured with bulleted args and a clear purpose at the start. It is somewhat lengthy due to many parameters, but each sentence adds value. Could be slightly more concise.

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?

Given the tool's complexity (11 params, no annotations, output schema exists), the description covers parameter semantics well but lacks broader context like usage guidelines and behavioral details on create vs update. It partially compensates with parameter info.

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

Parameters5/5

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

With 0% schema description coverage, the description fully explains all 11 parameters, including defaults and format hints. This adds significant value beyond the bare schema, enabling correct invocation.

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 'Create or update a custom app on the clock.' This is a specific verb+resource combination. It distinguishes itself from siblings like delete_custom_app and show_notification by focusing on custom app management.

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?

The description provides parameter details but lacks explicit guidance on when to use this tool versus alternatives. No when-not-to-use or exclusions are mentioned. The purpose implicitly suggests usage for custom app creation, but it could be clearer.

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/Jelloeater/ulanzi-mcp'

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