Cairn

Stripping non-standard outputSchema from tool definitions sent to providers

NousResearch/hermes-agent · cluster 137128 · agent

Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 2 PRs.

The members concern non-standard keys such as function.outputSchema (from MCP tools) being included in tool definitions sent to OpenAI-compatible providers, with a bug report citing HTTP 400 errors on strict backends like GLM. Two pull request titles propose removing these keys before sending; the titles alone don't confirm whether either was merged or whether the issue is closed.

Open issues1

  • Issue#137128[Bug]: `function.outputSchema` forwarded to OpenAI-compatible providers causes HTTP 400 on strict backends (e.g. GLM)

Open PRs2

  • PR#137133fix(chat): strip MCP output schemas from wire tools
  • PR#137141fix(tools): strip non-standard keys from tools[].function before sending to providers
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.00 means 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 Lab

At a glance

Subsystem
agent
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/137128.json
cluster/137128.md