UiChemy AI Website Creator

uichemy_export_astro

Export a project as an ASTRO website project (source code the user runs or hosts themselves: npm install && npm run dev, or deploy it to any static host). Returns a download link to a .zip that works for 15 minutes and up to 5 downloads; give the link to the user right away. Nothing goes online. Only generated pages are exported. Use this when the user asks for the code, an Astro project, a zip, or to host the site themselves. To put the site online on the user's own Cloudflare account instead, use uichemy_deploy_to_cloudflare; for a UiChemy-hosted WordPress site, uichemy_publish_site.

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>"
    },
    "name": "uichemy_export_astro"
  }
}

Input Schema

Name	Required	Description	Default
`pages`	No	Page names to export. Omit for every generated page.
`projectId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 21, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only reveal safety profile (readOnlyHint=false, openWorldHint=false, destructiveHint=false), so the description adds substantial behavioral context: the link expires in 15 minutes, is limited to 5 downloads, should be handed to the user immediately, nothing is published online, and only generated pages are exported. These are precisely the operational facts an agent needs and cannot get from structured fields.

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 artifact, followed by delivery constraints and routing to alternatives. Dense but every clause carries information; the parenthetical shell command is slightly verbose but useful to the user.

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?

With no output schema, the description carries the full return-value burden and does so: a download link to a .zip with an expiry and download cap. Combined with the usage routing and behavioral constraints, an agent has everything needed to call it and relay the result correctly.

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 50%: the `pages` param is documented in-schema but `projectId` is not. The description's 'Only generated pages are exported' hints at the pages scope without giving syntax or selection rules, and says nothing about projectId. Adequate baseline given the schema carries half the burden, but it does not compensate for the coverage gap.

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 (export) and resource (project as an Astro website project), and immediately clarifies the concrete artifact (source code the user runs/hosts, returned as a .zip). It explicitly distinguishes itself from the two closest siblings by naming uichemy_deploy_to_cloudflare and uichemy_publish_site with their respective conditions.

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?

Provides an explicit when-to-use trigger ('user asks for the code, an Astro project, a zip, or to host the site themselves') plus two named alternatives with the exact condition that selects each. Nothing is left to inference.

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?