{"version":"2.1.268","anchor":"tooluses-toolresults-validation-schema-renamed-fields","canonical_anchor":"tooluses-toolresults-validation-schema-renamed-fields","heading":"toolUses \/ toolResults validation schema renamed fields","tier":"internal","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/tooluses-toolresults-validation-schema-renamed-fields","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### toolUses \/ toolResults validation schema renamed fields\n\ntoolUses\/toolResults validation now expects tool_use_id and tool fields instead of id and name\n\n**What**\n\nThe internal validation for `toolUses` and `toolResults` data now checks for fields named `tool_use_id` and `tool`, rather than the previous `id` and `name`. The corresponding error messages were updated to match.\n\n**Why**\n\nThis is a naming change to the fields expected in this data; anything constructing these payloads directly needs to use the new field names to pass validation.\n\n- Area: SDK\n- Names: `tool_use_id`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}