mdr_ask
Resolve ambiguity mid-review by asking questions attached to specific file text; get inline answers to guide your edits.
Instructions
Ask the user one or more questions anchored to specific text in a file inside an active review session. Each question becomes an inline marker the user sees and can reply to in the md-redline UI. Returns with the reply text as soon as the user has answered every question, or with whatever partial replies exist when they finish the review (Done / Finish review), or empty-handed if the session ends another way. Replies also land in the marker threads on disk, so when this tool returns without reply text you should re-read the file(s) before concluding the user did not answer. Use this when a comment is unclear, or when you hit a planning fork while editing. Prefer asking over guessing when the right answer would meaningfully change your edit.
Only one mdr_ask can be pending per session at a time. If this returns "a previous mdr_ask is still pending", post a reply to the prior question via mdr_review (with a replies: payload targeting that commentId) — that resolves the pending ask in-place — and then retry mdr_ask with your new questions.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| questions | Yes | ||
| sessionId | Yes | Session ID from a previous mdr_review call, or the sessionId of an active mdr_request_review handoff. Both work: asking a clarifying question about a comment the user left during their own review is the primary use case. |