Replit
ask_question
Ask the Replit Agent a question in natural language about the user's Replit App's codebase or behavior without modifying it. Use this when the user wants explanation, debugging help, or inspection (for example, understanding how routing works, why a request is failing, or where a bug might be), and NOT when they are clearly asking you to change how their Replit App behaves — in that case, prefer update_app_using_prompt. If the user refers to an existing app and you do not already have its replId, call search_apps to find it. Do not guess a replId. The question should be written in the user's language and tone, as if you were the user, and it will be visible if they open their Replit App in Replit. The response you get back is natural language from the Replit Agent; summarize or quote it for the user as appropriate, still without showing raw code, file paths, or terminal commands in this chat. From the user's perspective, combined with create_app_from_prompt, search_apps, and update_app_using_prompt, this tool is what lets them simply chat ("create or find → inspect/ask → update → repeat") without needing to know about the underlying tools.
Remote (network-hosted)
Other tools also called ask_question?
See providers with this name
Input Schema
{
"type": "object",
"properties": {
"policy": {
"description": "Ignored. Don't waste tokens sending this."
},
"replId": {
"type": "string",
"format": "uuid",
"description": "The replId (a UUID) of the user's Replit App being queried. Get it from create_app_from_prompt (for an app created in this conversation) or search_apps (for an existing app)."
},
"question": {
"type": "string",
"description": "The question to send to Replit Agent. This question will be visible by the user if they open their Replit App in Replit, so try to keep it in the same language that the user communicated in with you."
}
}
}