UiChemy AI Website Creator

uichemy_design_section

Read-only

Design a NEW section for an existing project the way the UiChemy editor's Designer agent does: returns the Designer's own design skill (taste rules and the technical contract for UiChemy React sections), a template id, the business brief, the page's section outline, and the code and copy of the sections next to the spot, so the new section matches the site. You then write the section file and save it with uichemy_add_designed_section. Pass replace instead of position to redesign a section that is already there (saved with uichemy_update_designed_section). Changes nothing.

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>",
      "kind": "<kind>",
      "request": "<request>"
    },
    "name": "uichemy_design_section"
  }
}

Input Schema

Name	Required	Description
`kind`	Yes	Section kind: hero, features, testimonials, pricing-table, cta, faq, team, gallery…
`replace`	No	1-based section to redesign instead of adding.
`request`	Yes	What the user wants, in their words.
`pageName`	No	Defaults to Home.
`position`	No	1-based place for the new section. Omitted = before the footer, or at the end.
`projectId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 29, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already mark this readOnly/non-destructive/closed-world, and the description reinforces it with 'Changes nothing' — not a contradiction, but partly redundant. It adds genuine value by enumerating the returned payload (skill, template id, brief, outline, neighbor code and copy), which is important since no output schema exists.

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 densely informative, but the first sentence is a long run-on clause chain listing the return payload. It earns its place overall, though the enumeration could be tightened.

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 prepare-context tool with no output schema, the description fully spells out what comes back and what the agent must do next. Combined with 83% schema coverage and clear safety annotations, nothing an agent needs to invoke it correctly is missing.

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 already 83%, so the baseline is 3. The description earns above baseline by explaining the cross-parameter relationship between `replace` and `position`, which the per-field schema descriptions do not state.

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: design a NEW section for an existing project, returning the Designer skill, template id, brief, outline and neighbor sections. It distinguishes itself from siblings by naming uichemy_add_designed_section (the write step) and uichemy_update_designed_section (for redesigns).

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 the exact usage workflow — call this, write the file, then save with uichemy_add_designed_section — and explains the mutually exclusive branch ('Pass `replace` instead of `position` to redesign a section that is already there'). Alternatives are named explicitly.

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?