--- name: ironbee-search-scenario description: "Find reusable IronBee verification scenarios by name, description, or metadata in the scenario store, using the ibdt_scenario-search / ibdt_scenario-list MCP tools." disable-model-invocation: true --- # IronBee — Search scenarios > **⚠️ Run this inline — do NOT delegate.** Do every step yourself, in this conversation; > do **not** use the `Task` tool or spawn a sub-agent. A sub-agent runs as a separate session, > so its tool calls are recorded elsewhere and the work won't be tracked correctly. Find saved verification **scenarios** using the devtools scenario tools directly. Read-only. ## Steps 1. **Pick the surface:** - **`ibdt_scenario-search`** (fuzzy, ranked over name + description) — discovery ("find login scenarios"). - **`ibdt_scenario-list` with `metadataMatch`** — precise structural lookup ("which scenarios cover `src/auth/login.ts`"). Metadata is NOT indexed by `ibdt_scenario-search`, so path/tag lookups use `ibdt_scenario-list`. 2. **One server, one search** — all scenarios live in the single `ironbee-devtools` store, so one `ibdt_scenario-search` / `ibdt_scenario-list` covers everything (no union across servers). 3. **Report** name + description + platform + (for fuzzy search) relevance score; surface scope. The platform sections below give each enabled cycle's tool prefix + what to test. All cycles share ONE `ironbee-devtools` server, the shared `ibdt_scenario-*` tools, and the flat `.ironbee/scenarios` store (you pass `scope`; the server resolves the path — no per-prefix subdir). A single scenario script MAY call tools across platforms in one flow — author it as ONE scenario, not split per platform.