UiChemy AI Website Creator

uichemy_create_project

Creates a new UiChemy project from layouts in the UiChemy template library, using the copy, fonts and colours passed in. It is the only way to start a project here: every site is built from the template library, and HTML, CSS or JavaScript written elsewhere is not imported. For library sections as code in the user's own React app, uichemy_get_page_code is the tool. Each page is a list of sections, normally a navbar first and a footer last; a home page usually has 8 to 12 sections (hero, social proof, features, how it works, testimonials, pricing or offer, FAQ, CTA) and an inner page 5 to 8. Text and image slots belong to the layout: uichemy_template_slots lists them with their maximum length and what each one is for. A slot left empty shows its token on the page, an image slot left empty keeps the template's stock photo, and copy over a slot's limit makes the whole call fail. Two sections using the same layout share the same copy. Image slots take urls, so a generated picture needs to be uploaded first. category files a page in the sitemap (Blog, Legal, Site Extras...); pages without one are filed under Core Pages. brief fills the project's Scope tab and is required, as are headingFont, bodyFont and all five palette colours. The result names any slot left unfilled and any layout that was not found.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	The project's name. When the user has not named the business, a fitting name works; it can be renamed later in UiChemy.
`brief`	No	The project's Scope — what the business is, who it serves and what the site must do. This fills the Scope tab; without it the project opens with an empty brief.
`pages`	Yes	Pages in order; the first is the home page.
`palette`	Yes	All five slots, as #RGB or #RRGGBB.
`bodyFont`	Yes	A Google Font family name for body text.
`headingFont`	Yes	A Google Font family name for headings.
`createCanvas`	No	Also do what the editor's "Continue to design" does on first open — colour roles, the section style's band colours, the export section list, every page marked built — with no AI call, so the project needs no editor visit. Same as uichemy_create_canvas afterwards.
`sectionStyle`	No	With createCanvas: the section style to pin (default subtle_01). Without one the canvas rolls a random one.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only give the generic safety profile (not read-only, not destructive, closed-world). The description adds genuinely non-obvious behavior: empty text slots render their token, empty image slots keep stock photos, copy over a limit fails the entire call, duplicate layouts share copy, image slots require URLs so generated images must be uploaded first, and the response names unfilled slots and missing layouts.

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?

Front-loaded with the core action and the 'only way to start a project' constraint before details. It is long and dense, but nearly every sentence carries distinct operational information rather than filler; a small amount could still be trimmed.

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 an 8-parameter, deeply nested mutation with no output schema, the description covers the essentials an agent needs: required inputs, the slot/failure contract, global-section sharing, and what the result reports. Nothing critical is left unstated.

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 the baseline is 3, but the description still adds meaning: `category` files a page in the sitemap and falls back to Core Pages, `brief` fills the Scope tab and is required, and headingFont/bodyFont/five palette colours are mandatory. It does not restate every nested SEO field, which is reasonable given the schema documents them.

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?

States a specific verb+resource ('Creates a new UiChemy project') plus the source ('from layouts in the UiChemy template library'). It also draws a hard boundary: 'It is the only way to start a project here' and explicitly names the sibling it is not (uichemy_get_page_code).

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?

Gives explicit when-to-use ('the only way to start a project'), when-not ('HTML, CSS or JavaScript written elsewhere is not imported'), and routes the alternative case to uichemy_get_page_code. It also points to uichemy_template_slots for discovering the slot contract before calling.

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?