News for hackers. Stuff that matters.

A comment on Le Chat. Custom MCP Connectors. Memories. Parent comment

Re:Le Chat. Custom MCP Connectors. Memories by fumeux_fume on Thursday September 04, 2025 @10:45AM (#45127884)
Very common struggle, but a great way to prevent that is prefilling the assistant response with "{" or as much JSON output as you're going to know ahead of time like '{"response": ['
[ Parent | on HN ]
Re:Le Chat. Custom MCP Connectors. Memories by XenophileJKO on Thursday September 04, 2025 @11:47AM (#45128591)
Just to be clear for anyone reading this, the optimal way to do this is schema enforced inference. You can only get a parsable response. There are failure modes, but you don't have to mess with parsing at all.
[ Parent | on HN ]
Re:Le Chat. Custom MCP Connectors. Memories by psadri on Thursday September 04, 2025 @11:20AM (#45128284)
Haven’t tried this. Does it mix well with tool calls? Or does it force a response where you might have expected a tool call?
[ Parent | on HN ]
Re:Le Chat. Custom MCP Connectors. Memories by fumeux_fume on Thursday September 04, 2025 @12:30PM (#45129068)
It'll force a response that begins with an open bracket. So if you might need a response with a tool call that doesn't start with "{", then it might not fit your workflow.
[ Parent | on HN ]