UiChemy AI Website Creator

uichemy_replace_section

Destructive

Swaps a section for another LIBRARY layout. To replace it with a NEW design made for this site ("generate / design a new hero", "make it more creative"), use uichemy_design_section with replace and then uichemy_update_designed_section instead. Swap the layout rendering at one position — same slot, different template. The copy does NOT carry over: slot tokens belong to the template, so the new one has its own and will render them raw until filled. Call uichemy_template_slots for the new layout and pass text.

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>",
      "pageName": "<pageName>",
      "index": "<index>",
      "kind": "<kind>",
      "variant": "<variant>"
    },
    "name": "uichemy_replace_section"
  }
}

Input Schema

Name	Required	Description
`kind`	Yes
`text`	No
`index`	Yes	1-based, as uichemy_get_page lists them.
`variant`	Yes
`pageName`	Yes
`projectId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds the concrete consequence an agent cannot get from them: copy does NOT carry over because slot tokens belong to the template, so the new layout renders tokens raw until filled. It also prescribes the recovery path (call uichemy_template_slots for the new layout and pass `text`).

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 sibling routing, then the behavioral caveat. Slightly redundant — 'Swaps a section for another LIBRARY layout' and 'Swap the layout rendering at one position — same slot, different template' cover overlapping ground — but nothing is filler.

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, no-output-schema mutation this covers the highest-risk detail (copy loss and how to recover it) and routes to the right alternative. It doesn't state whether the replaced section is recoverable or what `index` refers to on the pre-swap page, a minor gap given the otherwise strong disclosure.

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 only 17% — only `index` is documented in the schema. The description adds real meaning for `text` (fill the new layout's slot tokens) and implies what `kind`/`variant` select, but says nothing about `projectId` or `pageName`, leaving half the parameters to inference.

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 and resource ('Swaps a section for another LIBRARY layout') and immediately clarifies the mechanism ('swap the layout rendering at one position — same slot, different template'). It is clearly distinguishable from uichemy_add_section and uichemy_design_section, both of which are named or implied.

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?

Explicitly names the alternative tool and the trigger phrase that selects it: for 'generate / design a new hero' or 'make it more creative', use uichemy_design_section with `replace` then uichemy_update_designed_section. The when-this/when-not-this split is fully spelled out.

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?