webmcp-gen

1# Generate and validate page WebMCP tools
2 
3Create a durable artifact that exposes a real page workflow through WebMCP and proves that the tool behaves like the existing UI.
4 
5## Output
6 
7Save the work under:
8 
9```text
10artifacts/<domain>/<task>/
11  manifest.json
12  webmcp.init.js
13  eval.json
14  eval-report.md
15```
16 
17## Workflow
18 
191. Define the user goal, required initial page state, allowed actions, and consequential actions that need explicit confirmation.
202. Explore the page with agent-browser. Record the existing UI behavior, success signal, failure states, and recovery path.
213. Write `manifest.json` with the goal, required state, available tools, expected calls, expected UI changes, recovery cases, and excluded secrets.
224. Create `webmcp.init.js` and `eval.json`. Prefer declarative WebMCP for semantic HTML forms. Use imperative tools only when the workflow cannot be expressed declaratively.
235. Load the script before navigation:
24 
25```bash
26agent-browser --init-script ./webmcp.init.js open https://example.com
27agent-browser webmcp list
28agent-browser webmcp invoke <tool> --params @fixture.json
29```
30 
316. Validate registration metadata, input validation, invocation results, visible UI effects, navigation or frame cleanup, invalid state recovery, cancellation, and timeout behavior.
327. Save deterministic checks and agent eval cases. Compare at least one task against the accessibility-tree fallback and record success, tool calls, latency, and token use when an external agent is available.
33…