From e2d55e1caf10c683ed90a74b0b054018e302a795 Mon Sep 17 00:00:00 2001 From: Don Garrett Date: Tue, 13 Oct 2026 19:11:49 +0000 Subject: [PATCH] Architecture X3: avoid, not reject, search-then-dispatch meta-tools A special-purpose MCP server that works that way may still be worth it. Co-Authored-By: Claude Opus 5.5 (1M context) Claude-Session: https://claude.ai/code/session_01J5Utyfzw7gF7UhjRDEtjTk --- docs/Architecture.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/Architecture.md b/docs/Architecture.md index d926d6e..9e9c36f 100644 --- a/docs/Architecture.md +++ b/docs/Architecture.md @@ -974,8 +974,10 @@ so every upstream action traces to one agent. - **One instance per (service, site, privilege),** each with its own credentials, so a wrong-site or wrong-privilege action needs a tool that isn't mounted. - **Per-task tool profiles** mount only what a work item's scope needs. -- **Rejected: search-then-dispatch meta-tools** over large catalogues (extra round +- **Avoid search-then-dispatch meta-tools** over large catalogues (extra round trips for a local driver, opaque arguments, a tool list that defeats caching). + A special-purpose server that works that way may still be worth it, as a + deliberate exception. ### X4. Images, VMs and restarts -- 2.54.0