Skip to main content
Glama

UiChemy AI Website Creator

uichemy_site_versions

Read-only

List the versions of a project's static site on the user's own Cloudflare (what uichemy_deploy_to_cloudflare, or the editor's Publish > Astro frontend / HTML / React / Next.js, put online). Every publish or resync is a numbered version: which one is LIVE, what changed in each, who published it and when. Use it before uichemy_restore_site_version, or when the user asks what was published. Not for EmDash (CMS) sites.

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

Input Schema

NameRequiredDescriptionDefault
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/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 real context beyond that — versions are numbered, each carries LIVE status, diff summary, publisher identity and timestamp, and they live on the user's own Cloudflare rather than uichemy's. Nothing contradicts the annotations, though pagination or result-size behavior is not mentioned.

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, then usage routing and exclusions; every clause conveys information. The parenthetical listing output channels (Astro/HTML/React/Next.js) is slightly verbose but helps identify where versions come from.

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 single-parameter read-only listing tool with annotations and no output schema, the description covers origin of data, what each version contains, live-state, authorship/time, and sibling routing — everything an agent needs to call it 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?

Only one parameter (projectId) exists and schema description coverage is 0%, so the description carries the burden; it implies project scoping throughout ('a project's static site') but never names the parameter or states its expected format/id source. Adequate but not compensatory.

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 ('List the versions of a project's static site') and scopes it to the user's own Cloudflare account, explicitly naming the writing siblings (uichemy_deploy_to_cloudflare, Publish frontends) that create those versions. An agent can distinguish it from uichemy_deploy_to_cloudflare, uichemy_publish_status and uichemy_restore_site_version 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?

Gives explicit triggers — 'Use it before uichemy_restore_site_version, or when the user asks what was published' — plus an explicit exclusion, 'Not for EmDash (CMS) sites', which routes CMS users to the uichemy_emdash_status / publish_emdash siblings.

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