Skip to main content
Glama

UiChemy AI Website Creator

uichemy_download_site

Download a project as SOURCE CODE the user hosts themselves, as a .zip behind a link (works for 15 minutes and up to 5 downloads; give the link to the user right away). Nothing goes online. Frameworks: html, astro, react, next. Astro, React and Next.js come plain or with a CMS: astro: none or emdash; react: none or sanity; next: none, payload or sanity. ASK, DON'T GUESS: if the user has not named the framework, call without format and show them the question this returns; once they pick Astro, React or Next.js and have not said whether they want a CMS (or which), call without cms and show the CMS question this returns. Pass exactly what they chose. Only generated pages are included. To put a site online use uichemy_publish_site (WordPress) or uichemy_publish_emdash / uichemy_deploy_to_cloudflare (the user's own Cloudflare).

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_download_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
cmsNoThe CMS the user chose. astro: none | emdash. react: none | sanity. next: none | payload | sanity. Omit (for astro, react, next) to get the question to ask them. Not for html.
buildNoAstro + EmDash only. html = sections stay UiChemy designs (the default); astro = sections become Astro components whose text and images are edited in CMS fields. The two options the export screen offers.
pagesNoPage names to include. Omit for every generated page.
formatNoThe framework the user chose. Omit to get the question to ask them. (emdash = astro with cms emdash.)
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / build
      Added value: +{
      +  "description": "Astro + EmDash only. html = sections stay UiChemy designs (the default); astro = sections become Astro components whose text and images are edited in CMS fields. The two options the export screen offers.",
      +  "enum": [
      +    "html",
      +    "astro"
      +  ],
      +  "type": "string"
      +}
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the annotations: link lifetime (15 minutes), download cap (5), the instruction to hand the link over immediately, the fact that nothing is hosted, and the scoping rule that only generated pages are included. Annotations already cover readOnly/openWorld/destructive, so this added operational context is the right kind of contribution; only a note on what happens if the link expires or how regeneration works is missing.

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 constraints, then the ask-don't-guess protocol, then alternatives — a sensible ordering. It is dense but the ASK/DON'T GUESS block partially duplicates the enum descriptions in the schema, so it's slightly longer than strictly necessary.

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 download tool with no output schema, the description supplies everything an agent needs: what the return value is (a link), its validity window and limits, what's excluded (ungenerated pages), and how to disambiguate framework/CMS choices. Nothing required for a correct call 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 80%, and the description still adds meaning: the framework/CMS compatibility matrix (astro: none|emdash, react: none|sanity, next: none|payload|sanity) and the rule that omitting `format`/`cms` returns a question rather than defaulting. That omission-as-protocol detail is not obvious from the enums alone, though it does restate some of the schema text verbatim.

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 ('Download a project as SOURCE CODE ... as a .zip behind a link') and immediately scopes it: self-hosted source, nothing goes online. It explicitly contrasts itself with the publishing siblings (uichemy_publish_site, uichemy_publish_emdash, uichemy_deploy_to_cloudflare), so an agent can route without opening a schema.

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?

Names the alternatives and the condition that selects them ('To put a site online use ...'), and adds an explicit decision protocol: call without `format` / `cms` to surface the question when the user hasn't chosen. This is exactly the when-to-use / when-not-to-use / which-alternative triad.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources