From 25cb2f5bb66607ce29b6a3ca0415394f87694cb9 Mon Sep 17 00:00:00 2001 From: Claude Date: Mon, 14 Sep 2026 08:57:16 +0000 Subject: [PATCH] docs: correct the Zapier mcp-registry partition counts (58, not 60) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit READ_ONLY holds 25 methods, not 27 — the previous figure counted the strings "waiting" and "error" from the getActionRun comment. The registry itself returns 58 methods, and is byte-identical at 0.103.0 and 0.111.1, so the pending SDK bump needs no reclassification. Verified by enumerating sdk.getRegistry({ package: "mcp" }) at both versions and diffing against the three classification sets. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01PVrtz6XV3M8zxBttQUYKBz --- CLAUDE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CLAUDE.md b/CLAUDE.md index fee5d4d..fbe8098 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -38,7 +38,7 @@ Mastra instance + server config: `agents/src/mastra/index.ts` - Parameter names come from the SDK's Zod schemas — read them from the registry, never guess - Table operations use `table` (not `tableId`) - Record creation uses `{ data: {...} }` wrapper per record -- The three sets below must partition the mcp registry exactly — **10 + 27 + 23 = 60 methods** at SDK 0.103.0. The `zapier-sdk-tools` unit test asserts it; re-check the counts after every SDK bump. +- The three sets below must partition the mcp registry exactly — **10 + 25 + 23 = 58 methods** at SDK 0.103.0 (unchanged through 0.111.1). The `zapier-sdk-tools` unit test asserts it; re-check the counts after every SDK bump. - `APPROVAL_REQUIRED` set: 10 write/delete tools need human approval - `READ_ONLY` set: 27 discovery tools (used for MCP annotations + agent-level background execution) - `EXCLUDED_METHODS` set: 23 methods skipped during tool generation — deprecated wrappers (`request`, the `*Authentication` duplicates of the `connection`-prefixed methods, the `*InputField*` aliases) plus surfaces Foreman doesn't expose (Connect-Builder OAuth client-credentials; the blocking `createConnection`/`getConnectionStartUrl`/`waitForNewConnection` helpers; the trigger-inbox lifecycle + lease/ack methods that `lib/trigger-inbox/` drives directly)