# NousResearch/hermes-agent · XML tool calling loop with nested data params

## Open now

- Nothing open on GitHub.

A bug causes an agent to loop when XML tool calling encounters nested JSON objects or empty data payloads, resulting in 400 Bad Request errors. Two fixes address this by resolving the XML tool calling loop for nested data parameters.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #8982. Verify it addresses your case.
- **Recommended:** read PR #8982 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-8982`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Closed / duplicate issues

- #8912: \[Bug\]: Agent loops on 400 Bad Request due to empty data={} payload (XML tool calling issue with nested JSON objects)

## Prior & competing PRs

- **#8982: fix(homeassistant): resolve XML tool calling loop for nested data params**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `tests/tools/test_homeassistant_tool.py`, `tools/homeassistant_tool.py`
- **#8918: fix(homeassistant): #8912 resolve XML tool calling loop by casting ne…**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `#8982`

## Fix status

- Merged to main in PR #8982 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-04-13`. This confirmation is old and may be out of date (a revert/reopen would not have invalidated it here); re-verify.