{"version":"2.1.273","anchor":"unverified-tool-call-warning-now-checks-argument-schema-not","canonical_anchor":"unverified-tool-call-warning-now-checks-argument-schema-not","heading":"Unverified-tool-call warning now checks argument schema, not just call history","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/unverified-tool-call-warning-now-checks-argument-schema-not","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Unverified-tool-call warning now checks argument schema, not just call history\n\nWarning about calling untested connector tools from an Artifact page now tells Claude to check the tool's argument schema too\n\n**What**\n\nWhen an Artifact page calls a connector tool that hasn't had a successful call observed during the current session, Claude Code shows a warning about that. The warning message now adds a new instruction: check the page's argument names against each tool's input schema, if the session has access to that tool, and treat the result fields the page reads as unverified unless a real, safe call can confirm them.\n\n**Why**\n\nThis gives Claude a concrete way to partially verify an untested tool call, by checking argument names against the schema, rather than treating every unverified call the same way.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}