You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: Introduce Tracking of Used Auth and Bound Keys in parse_tool for Client Strictness
This commit introduces functionality to the `parse_tool` helper to identify and report which bound and authentication keys are actively used during tool parsing. This is a foundational step towards implementing a more robust and predictable client through a new `strict` mode.
The ability to determine used keys will allow the client to:
* Provide errors when users supply unnecessary authentication or bound parameters (in non-`strict` mode).
* Enforce that all provided authentication and bound parameters are consumed by the loaded tools, ensuring no extraneous or potentially misleading information is present (in `strict` mode).
0 commit comments