fix: rename invalid property keys in get_legal_intakes tool schema (fixes EU clm_connector failures)#67
Draft
sd-gh-bot wants to merge 1 commit into
Draft
Conversation
Claude Sonnet 4.5 on Vertex AI enforces that tool input_schema property
keys match the pattern '^[a-zA-Z0-9_.-]{1,64}$'. The previous schema
had keys like 'filter__priority[$eq]', 'filter__status[$in]' etc.
which contain '[', ']', and '$' — all disallowed characters.
This caused the entire clm_connector node to fail in sidebar-prod-eu
with HTTP 400 'invalid_request_error' and no fallback available.
Changes:
- Rename 'filter__priority[$eq]' → 'filter__priority' (eq is now the default)
- Rename 'filter__priority[$ne]' → 'filter__priority_ne'
- Rename 'filter__priority[$in]' → 'filter__priority_in'
- Rename 'filter__status[$eq]' → 'filter__status' (eq is now the default)
- Rename 'filter__status[$ne]' → 'filter__status_ne'
- Rename 'filter__status[$in]' → 'filter__status_in'
- Update handler to emit the correct API query param for each renamed key
(e.g. filter__priority → filter__priority[$eq] in URLSearchParams)
Observed in: sidebar-prod-eu GCP logs, chat_ids ecef3457 and 1796892a
Evidence: tools.18.custom.input_schema.properties: Property keys should
match pattern '^[a-zA-Z0-9_.-]{1,64}$'
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
2 participants
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.
User description
Problem
The
get_legal_intakestool schema contained property keys with characters that violate Vertex AI Claude Sonnet 4.5's strict pattern requirement:^[a-zA-Z0-9_.-]{1,64}$Invalid keys in the previous schema:
filter__priority[$eq],filter__priority[$in],filter__priority[$ne]filter__status[$eq],filter__status[$in],filter__status[$ne]Characters
[,], and$are not in the allowed set.Impact
This caused every
clm_connectoragent call to fail with HTTP 400 insidebar-prod-eu(and also regions where claude-sonnet-4-5@20250929 is used). No fallback model was available.Evidence from GCP logs (
sidebar-prod-eu):Affected chat_ids: ecef3457, 1796892a — recurring across the 12h window.
Fix
Rename the invalid property keys to use only alphanumeric + underscore chars. The handler emits the correct API query params so the backend API contract is unchanged.
Validation
Generated description
Below is a concise technical summary of the changes proposed in this PR:
Update the
getLegalIntakesToolinput schema to rename filter properties to pattern-compliant keys and clarify operator descriptions for each priority and status enum. Adjust thegetLegalIntakesrequest handling so it preserves the existing backend query parameters while using the new request field names.[$eq],[$ne], and[$in]params fromgetLegalIntakeswhile mapping to the renamed request fields.Modified files (1)
Latest Contributors(2)
getLegalIntakesToolinput schema.Modified files (1)
Latest Contributors(2)