Three tools with basic descriptions but significant gaps in schema completeness and parameter documentation. create_preview has a reasonable description (145 chars) and partial input schema, but lacks output schema documentation. list_previews and stop_preview have minimal descriptions (under 50 chars) and empty input schemas. No parameter descriptions visible in any tool. Error handling guidance is absent. Tool names follow verb_noun convention (positive), but parameter constraints and output structures are undocumented.
Create a public HTTPS preview URL for the web app running in this project, so a human or another agent can review it. Detects the dev server automatically. Returns a stable URL (same repo+branch always gets the same URL). IMPORTANT: after calling this, include the returned URL in your reply to the user so they can open it. Make sure the dev server is actually running first.
List active preview URLs for the current repo and branch.
Tear down the active preview(s) for the current repo and branch.
list_previews and stop_preview have descriptions under 20 characters with no parameter or output documentation
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields without knowing response structure.
create_preview parameters (port, name, ttl) lack descriptions explaining their purpose, format, and constraints
No error handling guidance. Tools do not indicate what to do if dev server is not running, port is invalid, or preview creation fails.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 45 | 2026-07-28+ | v2 |
create_preview description mentions 'auto-detect' but no parameter constraints or validation rules are documented for port, name, or ttl formats