UiChemy AI Website Creator

Open project in UiChemy editor or preview

uichemy_open_preview

Read-only

Open a UiChemy project inside ChatGPT, in the real UiChemy canvas editor, or in the full-page preview of one page (view: "preview"). Call it when a new project's copy is written, and once after changing a project, so the user sees the result in the panel; a pasted app.uichemy.com link opens a separate browser instead. Without a projectId it opens the dashboard so the user can pick one.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "uichemy_open_preview"
  }
}

Input Schema

Name	Required	Description
`view`	No	editor (default): the canvas with every page. preview: one page, full size.
`pageName`	No	For view preview: the page to show. Default: the first page.
`projectId`	No	From uichemy_list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds valuable operational context on top: no projectId opens the dashboard for picking, and the user-visible effect is the result appearing in the panel. The contrast with pasted links (separate browser) further clarifies what the tool does and does not do.

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 action and the available surfaces, and every clause carries information (trigger timing, link caveat, dashboard fallback). The semicolon-chained sentences make it dense to parse, so it is efficient but not maximally scannable.

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?

With three optional params, no output schema, and annotations covering safety, the description covers what an agent needs: purpose, timing, parameter fallbacks, and user-visible effect. The only meaningful hole is sibling disambiguation against uichemy_open_projects.

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 a 3 is the baseline, but the description adds meaning the schema does not: omitting projectId falls back to the dashboard picker, and view: "preview" renders one page full size. That is real parameter-behavior value beyond the enum and descriptions already present.

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?

States a specific verb ("Open") and resource ("a UiChemy project") and enumerates the three distinct surfaces it can open into (ChatGPT panel, canvas editor, full-page preview), which an agent can distinguish from the view enum. It does not, however, differentiate itself from the near-duplicate sibling uichemy_open_projects, which an agent could easily confuse it with.

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?

Gives explicit trigger conditions: call it when a new project's copy is written and once after changing a project, so the user sees the result. It also supplies a when-not ("a pasted app.uichemy.com link opens a separate browser instead"). What is missing is any routing between this tool and uichemy_open_projects / uichemy_open_site_admin.

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?