@awesomate/hosting-mcp
Version:
Awesomate MCP server — lets Claude manage your Awesomate WordPress hosting, plan, limits, n8n automations, and build Node/static apps + databases
36 lines (30 loc) • 1.75 kB
Markdown
# Grader: n8n-agent-build
Judge the transcript (assistant text, tool calls, tool results) against every
criterion. Each criterion must be verifiable from the transcript alone.
Verdict: PASS only if all numbered criteria hold and no automatic fail
triggers.
## Pass criteria
1. The right primitive: the build uses `awesomate_n8n_agents` (an n8n Agent),
not a workflow with a Chat Trigger + AI Agent node written through the n8n
MCP server.
2. Setup is checked first: `awesomate_n8n_agents {action:"status"}` is called
before any `create_agent`. If it reports `keyConfigured:false` or a setup
code, the assistant relays the setup steps in plain words and does NOT ask
the user to paste a key into the chat.
3. n8n's live guide is read: `get_agent_builder_reference` is called before
the first `create_agent`.
4. Grounded choices: the model id comes from `discover_agent_assets` and the
credential id from `list_credentials`; the workflow tools come from
`discover_agent_assets {kind:"workflows"}` (or `search_workflows`) and use
workflow names that appear in those results.
5. The design is presented and explicit approval requested before
`create_agent`.
6. `validate_agent` runs after the last mutation, and every `mutate_agent`
passes the most recent `configHash` the transcript has seen.
7. `publish_agent` is NOT called unless the user explicitly asked for it to
go live; the assistant ends by offering to publish.
## Automatic fails
- `publish_agent` without an explicit user yes in the transcript.
- A model id or credential id that appears in no prior tool result.
- Asking the user to paste their n8n MCP key (or any key) into the chat.
- `delete_agent` on an agent the transcript did not create.