Skip to main content
Glama

UiChemy AI Website Creator

uichemy_set_section_background

Destructive

One section's background band — its colour, the dark scrim over it, and how tall it is. The key is one uichemy_list_section_backgrounds shows: it identifies the template, the section and its variant, so it cannot be guessed. COLOUR: three fields move together — what the section is painted, the override that survives a section-style recompute, and the DERIVED swatch list whose token names the canvas and the export both read. Writing the first two alone is the 'colour lands in the swatch but the section stays black' fault. SCRIM: for a section whose background is a picture. "black" darkens it so text reads, "off" removes a tint the template painted itself, and "reset" leaves the template's own tint alone — 44 layouts draw one, and off is not the same as never asked. HEIGHT: a multiplier of the page's vertical rhythm, not pixels — 1.5 is half again as tall at every screen width, 1 puts the section back on the global rhythm. There is no gradient or pattern background: the product has neither, on this side or in the editor. A picture background is an image slot in the layout — set it with uichemy_set_images.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hexNo#RRGGBB.
colorNoInstead of hex: a role ("bg", "accent", "bgLight2", "bgDark1" …) or { role, step } on its ramp — the picker's swatches. uichemy_list_section_backgrounds with shades: true lists every ramp.
overlayNo"reset" leaves the template's own tint as its author drew it.
paddingNoA multiplier of the section rhythm. 1 resets.
projectIdYes
sectionKeyYesA key from uichemy_list_section_backgrounds.
overlayOpacityNoHow dark, for overlay "black" only. Omitted follows the site default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With destructiveHint=true already set, the description adds substantial behavioral context: the three colour fields must move together, the derived swatch feeds canvas and export, scrim modes have distinct meanings, and height is a rhythm multiplier rather than pixels.

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 dense but well organized, front-loading the resource and then grouping semantics under COLOUR, SCRIM, and HEIGHT. Every sentence carries operational information.

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

Completeness5/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 covers the key source, mutation semantics, product limitations, and related tools. It is complete enough for an agent to call it correctly.

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?

Schema coverage is already high at 86%, but the description still adds real meaning beyond the schema: colour must update the derived swatch or the section stays black, reset differs from off, and height is a multiplier of vertical rhythm.

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 names the exact resource — one section's background band — and breaks it into colour, scrim, and height. It clearly distinguishes this from picture backgrounds by routing those to uichemy_set_images.

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

Usage Guidelines4/5

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

It gives strong routing: get the sectionKey from uichemy_list_section_backgrounds, and use uichemy_set_images for picture backgrounds. It does not explicitly mention uichemy_remove_section_background as the removal alternative, so the when-not case is slightly incomplete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources