Skip to main content
Glama
simonmak-ascent

mcp-vdd

by simonmak-ascent
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Clone Website

vdd_clone
Destructive

Crawl a target domain to produce a clone dataset and manifest, supporting WordPress schema inference and Next.js + Payload scaffolds.

Instructions

Crawl and capture a target domain into a clone dataset + manifest — WordPress-aware schema inference, Payload collections, and a Next.js + Payload + Postgres scaffold manifest (vdd/clone-manifest.json). Pass the domain as description. Writes vdd/clone-dataset.json, vdd/clone-manifest.json, and vdd/clone.md, overwriting any existing versions in place. Open-world: makes network requests to the target site and reads its sitemap and same-origin links. Use for cloning an external site; it is not part of the VDD phase pipeline, so for the normal init→validate flow call those phase tools instead. Parameter relationships: description is the target domain and statement is the desired outcome (both optional); maxPages, timeoutMs, concurrency, crawl, and browser tune the crawl and refresh=true bypasses a cached dataset.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
crawlNoClone: run the crawl (default true)
browserNoClone: run browser/static capture (default true)
refreshNoClone: force re-crawl, ignore a fresh cached dataset
maxPagesNoClone: max pages to crawl, 1-5000 (default 200)
statementNoFreeform vision statement (required for vision)
timeoutMsNoClone: per-request timeout in ms, 1000-60000 (default 10000)
concurrencyNoClone: concurrent crawl workers, 1-16; above ~16 risks tripping the target site rate limit (default 8)
descriptionNoFreeform description input
projectRootNoProject root: directory that constitution.md and the vdd/ folder are written to and resolved against. Relative paths resolve from the current working directory; keep the same value across every phase (default ".").

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
_sdtYesStrategy-and-Tactic instructions for the next step
errorNoError message when the phase fails
_phaseYesVDD phase that produced this result
outputNoAdditional structured phase output
successYesWhether the phase completed successfully
artifactNoPrimary artifact produced or returned
gateResultNoQuality-gate result, when the phase runs a gate

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.9.0
    • changedInput schema / properties / concurrency / description
      Previous value: -"Clone: concurrent crawl workers (default 8)"New value: +"Clone: concurrent crawl workers, 1-16; above ~16 risks tripping the target site rate limit (default 8)"
    • changedInput schema / properties / maxPages / description
      Previous value: -"Clone: max pages to crawl (default 200)"New value: +"Clone: max pages to crawl, 1-5000 (default 200)"
    • changedInput schema / properties / projectRoot / description
      Previous value: -"Project root: directory that constitution.md and the vdd/ folder are written to and resolved against (default \".\")"New value: +"Project root: directory that constitution.md and the vdd/ folder are written to and resolved against. Relative paths resolve from the current working directory; keep the same value across every phase (default \".\")"
    • changedInput schema / properties / timeoutMs / description
      Previous value: -"Clone: per-request timeout in ms"New value: +"Clone: per-request timeout in ms, 1000-60000 (default 10000)"
  2. Changed1 schema field changedv0.1.4
    • changedInput schema / properties / statement / description
      Previous value: -"Freeform vision statement (required for vision/e2e)"New value: +"Freeform vision statement (required for vision)"
  3. Changed1 schema field changedv0.1.3
    • changedInput schema / properties / projectRoot / description
      Previous value: -"Path to project root directory"New value: +"Project root: directory that constitution.md and the vdd/ folder are written to and resolved against (default \".\")"
  4. Changed1 schema field changedv0.1.2
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "_phase": {
+      "description": "VDD phase that produced this result",
+      "type": "string"
+    },
+    "_sdt": {
+      "description": "Strategy-and-Tactic instructions for the next step",
+      "type": "string"
+    },
+    "artifact": {
+      "description": "Primary artifact produced or returned",
+      "type": "string"
+    },
+    "error": {
+      "description": "Error message when the phase fails",
+      "type": "string"
+    },
+    "gateResult": {
+      "additionalProperties": false,
+      "description": "Quality-gate result, when the phase runs a gate",
+      "properties": {
+        "checks": {
+          "description": "Number of checks run",
+          "type": "number"
+        },
+        "passed": {
+          "description": "Whether the quality gate passed",
+          "type": "boolean"
+        },
+        "total": {
+          "description": "Total number of checks",
+          "type": "number"
+        }
+      },
+      "required": [
+        "passed",
+        "checks",
+        "total"
+      ],
+      "type": "object"
+    },
+    "output": {
+      "additionalProperties": {},
+      "description": "Additional structured phase output",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "success": {
+      "description": "Whether the phase completed successfully",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "_phase",
+    "_sdt"
+  ],
+  "type": "object"
+}
  5. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag openWorldHint and destructiveHint, and the description adds the crucial specifics: which files get written and that they are overwritten in place, plus the network/sitemap access and the refresh cache-bypass behavior. This goes beyond what the annotations state.

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 outputs, and every sentence carries information. It is dense and somewhat run-on in the parameter-relationships tail, keeping it just short of 5.

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 an output schema present, the description needn't detail return values, and it still names the output artifacts. For a 9-param open-world tool, all safety, side-effect, and usage context an agent needs is present.

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 the schema baseline is 3, but the description adds real meaning: it clarifies that 'description' is the target domain and 'statement' is the desired outcome, and groups maxPages/timeoutMs/concurrency/crawl/browser as crawl tuning. That resolves the vague 'Freeform description input' schema text.

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 specific verbs (crawl, capture) and the exact resource/artifact produced (clone dataset + manifest with named files). It explicitly distinguishes itself from the VDD phase siblings by noting it is not part of the phase pipeline.

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 when-to-use ('Use for cloning an external site') and when-not, routing the agent to the phase tools for the normal init→validate flow. This is a direct alternative-selection rule.

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

Deploy Server

Other Tools