test_cap
Run a Cap's connection test and end-to-end self-test, and record both results on its publishing checklist. Do this after publish_cap, before submit_cap. The connection test sends three requests to base_url + /qumge/ping (correctly signed, wrong secret, and a 10-minute-old timestamp — only the first may succeed); the end-to-end test calls one free and one billable operation directly on the Cap (nothing is charged) and, for a route the Cap reports itself, waits 2 seconds for its usage report. An MCP Cap has each listed tool called once instead. It warns (without blocking) about billed operations that have no doc. Needs the developer's Qumge key. (Older clients may still call this tool as test_app.)
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | The Cap's slug. | |
| qumge_key | No | Optional: your Qumge API key, for clients that cannot set an Authorization header. Takes precedence over the header. Never echoed back. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | ||
| missing | No | ||
| connection_passed | No | ||
| end_to_end_passed | Yes | ||
| connection_summary | No | ||
| end_to_end_summary | No |