Available tools and capabilities for route classification. Use to decide plan (requires execution) vs conversational (chat only) vs informational_search (fact lookup).
name router-tools-reference description Available tools and capabilities for route classification. Use to decide plan (requires execution) vs conversational (chat only) vs informational_search (fact lookup). metadata {"triggers":["route","tools","capabilities","plan","conversational","email","inbox","summary","gmail","imessage"]} Router Tools Reference Use this to decide if a user query requires plan (execution/automation), conversational (chat only), or informational_search (web/fact lookup). integration.google.workspace Operation User intent examples Route gmail.list "check my emails", "list inbox", "show unread", "any new emails", "what's in my inbox" plan gmail.read "read this email", "open email from X" plan gmail.draft_reply "draft reply", "reply to latest email", "respond to that email" plan inbox.triage "email summary" , "give me email summary" , "summarize my emails" , "email summary for today" , "inbox summary" , "triage inbox" plan gmail.send_draft / update_draft / delete_draft Send, update, or delete drafts plan integration.imessage Operation User intent examples Route chat.list "list my messages", "show chats" plan message.read "read messages from X", "show texts" plan message.queue_send "send text to X", "message John" plan message.approval.approve / reject Approve or reject queued messages plan integration.spotify Operation User intent examples Route playback.play / pause / next / prev "play spotify", "pause", "next song" plan search.play "play jazz on spotify", "spotify play chill music" plan integration.govee Operation User intent examples Route device.list "list my lights", "govee devices" plan Browser / App / System browser.navigate, browser.search, browser.click, browser.extract, browser.fill_form app.open, app.close, app.focus, app.click_ui, app.keyboard_shortcut system.volume, system.brightness, system.execute, system.dark_mode, etc. Route Decision Rules plan when user asks for a concrete deliverable or action: "give me X", "get me X", "fetch X", "show me X" where X is email summary, inbox, messages, etc. "email summary", "summarize my emails", "email summary for today" → inbox.triage Any imperative that maps to the tools above Reminders, schedules, follow-ups, opportunistic tasks conversational for: Greetings (hi, hello, hey) Acknowledgments (thanks, ok, got it) Small talk with no requested execution "what do you see", "describe my screen", "what's on my screen" (assistant uses screen/context to answer) informational_search for: General factual questions (what is X, when did Y happen) Web lookup with no execution request Prefer plan when uncertain – if the user could be asking for something executable, choose plan.