Urgent.News

What's breaking now, across thousands of outlets.

Tech

Every Tool Parameter Is a Question Your Voice Agent Has to Ask

If you have ever designed a REST endpoint, you already know most of what it takes to give a voice agent tools. Name it well, keep the parameters tight, validate inputs, return something useful. The difference is the client. Your endpoint is not called by a frontend developer reading your docs. It is called by a language model that is taking dictation from a stranger on a phone line, in real time,…

Voice agents require careful design of tool parameters, much like REST endpoints. The key differences are the client (an LLM taking dictation from a caller) and the real-time, silent nature of the interaction. Retell AI tools follow two shapes: one with detailed schema and infrastructure IDs, and another with parameters that callers would naturally provide.

The latter shape is more effective, as it avoids unnecessary data from the model and focuses on what the caller can actually say. Every required parameter should be a question the agent asks, with server-side resolution of business logic.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Goose Lang and Flisk.sh 101: Same Repo, Different Processes

Part 5 of Goose lang and Flisk.sh 101. This is the join, and the join is a boundary. ./total is a Goose program. It prints and exits. The orders-api container is a Go process Flisk generated.

  • Goose Lang tutorial integrates with Flisk.sh, focusing on Goose-Flisk integration
  • ./total file is Goose program printing and exiting once executed
  • Flisk generates orders-api container, a Go process listening until stack stopped

The agent reported CI green, but the check had never run on the commit it pushed

The agent amended the diff to fold in a review note, force-pushed, opened the PR page, looked for the check it already knew was green, saw a passing badge, and wrote the summary: CI passes, ready to…

  • CI check reported as green, but never ran on pushed commit
  • Agent amended diff, force-pushed, opened PR assuming green status
  • Pipeline ran with previous commit, old green check remained visible

Flisk.sh 101: One service.json, Then a Health URL

Part 4 of Goose lang and Flisk.sh 101. Use the Go backend. Do not pass --language goose . Flisk turns service.json into a local Docker and Tilt stack. You own the manifest.

  • Flisk.sh converts service.json to Docker and Tilt stacks
  • Requires Node.js 22.12+, Docker, and Tilt for stack start
  • Health URL checks live service status after first boot

More from Thursday 22 October →