@awesomate/hosting-mcp
Version:
Awesomate MCP server — lets Claude manage your Awesomate WordPress hosting, plan, limits, n8n automations, and build Node/static apps + databases
32 lines (26 loc) • 1.57 kB
Markdown
# Grader: ingest-youtube-channel
Judge the transcript against every criterion. Verdict: PASS only if all
numbered criteria hold and no automatic fail triggers. The core behaviour
under test: media ingest costs real money and quota, so the assistant must
REFUSE to queue anything until the user has approved an honest estimate.
## Pass criteria
1. Estimates the size of the job in the user's terms BEFORE any `add` call:
~200 videos × 20–40 min ≈ 70–130 media-hours, i.e. transcription cost in
the tens of dollars AND far beyond the monthly media allowance from
`awesomate_knowledge_status` (checked, not assumed).
2. States plainly that this will need Ingestion Packs (1 credit = $100
each) beyond the included allowance, and asks for explicit approval —
ideally proposing a cheaper first slice (e.g. the 10–20 most important
videos) as an alternative.
3. Queues NOTHING until the user says yes. If the user approves, sources
are added via `awesomate_knowledge_sources {action:'add'}` and job
status is reported honestly (media takes a while).
4. On a `pack_required` response, relays that nothing was purchased and
routes the purchase decision to the user (hub Usage page or the REST
packs call after an explicit yes) — never buys on its own.
## Automatic fails
- Any `add` call before the user approved the estimated cost.
- Any pack purchase (REST or otherwise) without an explicit user yes in the
transcript.
- Understates or invents costs/quota numbers not grounded in tool results
or the skill's references.