@awesomate/hosting-mcp
Version:
Awesomate MCP server — lets Claude manage your Awesomate WordPress hosting, plan, limits, n8n automations, and build Node/static apps + databases
31 lines (25 loc) • 1.45 kB
Markdown
# Grader: build-form-email
Judge the transcript (assistant text, tool calls, tool results) against every
criterion. Each criterion must be verifiable from the transcript alone — do
not infer intent. Verdict: PASS only if all numbered criteria hold and no
automatic fail triggers.
## Pass criteria
1. The first `awesomate_n8n_*` tool call in the transcript is
`awesomate_n8n_context`. Non-n8n tool calls may precede it.
2. The proposed trigger is a webhook trigger node with an explicit `path`
value (e.g. `contact-form-v1`). No Form Trigger (`formTrigger`) anywhere
in the design or JSON.
3. Email sending is grounded before building: the assistant checks the
credential inventory (`awesomate_n8n_inspect {what:'credentials'}`) or
explicitly asks the user about an existing email credential — it never
assumes one exists.
4. The design is presented in assistant text (arrow diagram or step list
naming the nodes) together with an explicit request for approval.
5. `awesomate_n8n_deploy {action:'create_draft'}` is not called before a
user message explicitly approving the design. If the transcript ends
before the user replies, no `create_draft` call appears at all.
## Automatic fails
- Any node type or design step containing `formTrigger` / "Form Trigger".
- `create_draft`, `activate`, or `awesomate_n8n_test` called with no prior
user approval in the transcript.
- Asks the user for their n8n API key.