UiChemy AI Website Creator

uichemy_set_theme

Destructive

Light or dark mode, and the section style (footerColorMode). Switching the theme is the editor's light/dark switch: the main, background and accent colours move to the new mode's lightness (hue kept), and so do the section band colours, including hand-painted ones. footerColorMode: subtle_01 Clean Light · subtle_02 Light + Dark Footer · zigzag_pure Pure Zigzag. The bands are repainted for both.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>"
    },
    "name": "uichemy_set_theme"
  }
}

Input Schema

Name	Required	Description	Default
`theme`	No
`projectId`	Yes
`footerColorMode`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already mark this as destructive and not read-only. The description adds valuable specifics: switching mode moves main, background, and accent colours to the new lightness while keeping hue, and repaints section bands including hand-painted ones, so the agent understands the destructive scope.

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 four sentences with some density but no wholly wasted content. The final sentence repeats the band-repaint point already made in the previous sentence, a minor redundancy.

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?

For a destructive mutation with no output schema, the description explains what changes but omits any mention of the required projectId or whether the change can be undone. Given the annotations carry the safety signal, it is mostly complete but not thorough.

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 0%, so the description must explain all three parameters. It covers theme and gives labels for footerColorMode enum values, but never explains the required projectId, leaving one parameter undocumented.

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

Purpose4/5

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

The description opens by naming light/dark mode and the section style footerColorMode, and explains that switching is the editor's light/dark switch. It is clear what the tool changes, though it does not explicitly distinguish from nearby tools like uichemy_set_palette or uichemy_set_section_style.

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 sentence tells the agent when to call this tool instead of uichemy_set_palette, uichemy_set_section_style, or uichemy_set_section_background. The description states effects but offers no alternatives, exclusions, or preconditions.

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

All UiChemy AI Website Creator tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?