Agent devs debate: normalize tool API responses before feeding the agent, or let it cope?
Manuelgrnbostel · reddit · 2026-09-21
A developer highlights a recurring agent-engineering pain: different APIs describe the same real-world state with incompatible terms — one shipping API says "in transit," another uses a different label; the same goes for service names, error codes, and address fields.
The options: build a normalization layer so tools agree before the agent sees data, or hand raw responses to the agent and trust it to reconcile differences. The author is leaning toward skipping the extra layer but worries about consistency, and is asking the community for their approach.
More from coding & agent
- Jev guide: the System-1 model that only judges and never writes — xiaohu · 2026-09-21
- Opinion: If an agent can't buy your product, you're building last year's SaaS — diegoposts · 2026-09-21
- baoer_signal_grep 1.6.6 Adds a Jev Semantic Judgment Layer for Coding Agents via MCP — Deep_Bus_7488 · 2026-09-21
- Laya MPS Runs Jev-Style Typed Decisions Locally on Apple Silicon at ~32ms — afshinmeh · 2026-09-21
- px0 IDE boots in <1ms with 20MB memory, winning users over from Zed — arpit_bhayani · 2026-09-21
- 90%+ of code will be written by LLMs, yet human instruction volume keeps growing — timigod · 2026-09-21