New: Cookbooks and AI ExplanationsStep-by-Step recipes to solve problems connected to Roadmaps and Cheat Sheets. Need more details? Use AI buttons for structured and simple explanations with concrete examples throughout the whole platform.Take a look
Your coding agent guesses the database type or the auth method, gets it almost right, and you fix it after the fact every time.
What you'll have at the end
A tool that pauses with a structured elicitation form for the one missing detail, then finishes with the right answer
You need
A working MCP tool that already takes some arguments from the model, running on an SDK that lets you read the client's declared capabilities after setup, with one fact left over that the tool currently guesses instead of asking.
Not covered
Collecting the actual credential value once the method is known, which belongs behind the separate out-of-band URL flow, never a form field.
Leans on
The isError flag that keeps a failed MCP tool call recoverable
when the client fails partway through for a reason that is not a declined form, that recoverable-error pattern covers the return path.
Should your agent ask before it deletes, sends, or pays?
for a destructive action that needs a stop-and-confirm gate rather than one missing fact, that recipe covers the approval decision itself.
Checked 18 Aug 2026
Part of the MCP Servers Implementation cookbook