{"version":"2.1.280","anchor":"new-istransparentwrapper-hook-on-an-agenttool-adapter-int","canonical_anchor":"new-istransparentwrapper-hook-on-an-agenttool-adapter-int","heading":"New isTransparentWrapper() hook on an agent\/tool adapter interface","tier":"internal","area":"Tool Adapters","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-istransparentwrapper-hook-on-an-agenttool-adapter-int","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New isTransparentWrapper() hook on an agent\/tool adapter interface\n\nTool and agent adapters gain a new isTransparentWrapper() method, currently always false\n\n**Unclear.** The finding does not say what functionality will read this method or when it might start returning true.\n\n**What**\n\nThe interface used for tool-or-agent adapters gained a new method, `isTransparentWrapper()`, alongside its existing `prompt()` and `mapToolResultToToolResultBlockParam()` methods. Right now it always returns `false` for every adapter.\n\n**Why**\n\nThis lays groundwork for distinguishing adapters that just pass calls straight through from ones that add their own behavior, though no adapter currently reports itself as a transparent wrapper.\n\n- Area: Tool Adapters\n- Names: `isTransparentWrapper`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}