Strip tool name fields for strict provider compatibility
Cluster 30662 · agent. Data as of
Nothing open on GitHub. Fix merged in #90129 on 25 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #90129. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #90129. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address problems where internal tool_name or name fields in tool/function call messages cause schema mismatches with strict providers, particularly NVIDIA NIM and certain Hermes function-calling models.
Open issues0
Open PRs0
Fixes on record
-
#90129 fix(providers): strip name/tool_name from NVIDIA NIM tool messages
files:
contributors/emails/[redacted:email],plugins/model-providers/nvidia/__init__.py,tests/providers/test_e2e_wiring.py,tests/providers/test_provider_profiles.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#30674 Fix NVIDIA NIM tool message schema · merged via another change →
#90129
Closed issues · 1
- Closed#30662Hermes function calling fails with mistral-large-3-675b-instruct-2512 due to schema mismatch
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- agent
- Merged PRs
- #90129
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 25 Aug 2026