Repository navigation
Conversation
…iew FORM settings to the form tools update_view rejects every FORM settings call (the API's FORM update schema is empty with additionalProperties false), its settings description points to get_view_schema_by_type, which is not a tool, and no tool returns a FORM view's formToken, so agents cannot reach update_form or form_questions_editor. create_view and get_board_info (v1 and v2) now return formToken, the update_view description states that only TABLE views take settings, and a failed FORM settings call names the form tools to use.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
create_viewandget_board_inforeturnformTokenon FORM views, parsed fromview_specific_data_str. The raw string is not returned.update_viewsettings now says only TABLE views accept settings. FORM, DASHBOARD and APP views do not.update_viewthat sent settings keeps the API error and points atupdate_formandform_questions_editor.Expected metric impact
update_viewrejections (~37/week in October, none succeeding since 10-19) should drop. The tool no longer tells the model to send settings the API rejects.Made with Cursor