get next step
get_next_stepShow the user's next step in the job search as a card. With no scope it picks one from their data, with a line saying why: the setup trail while their roles aren't confirmed, else the pipeline's most urgent move, else the week's plan; use that for open questions like "what should I do next?" or "where do I start?". Scope setup is the setup trail in Compass OS: each setup stop (such as importing a resume) marked done or to do, with its effort, and what the next stop asks for; it never decides whether a request can be done, an unfinished stop blocks nothing. Scope today lists today's moves in the pipeline: counts (active, interviewing, offers, ready), the most urgent move (a follow-up, interview prep, or an application that's ready or missing a piece), the few after it, and any offer. Scope week summarizes the week: roles from the last scan worth a look, follow-ups due, interviews coming up, and one upkeep step; use it for "how's my week?" or "what needs me?". Read-only. Jobs updated from Gmail or Calendar show only in the card.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "get_next_step"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| scope | No | Which card: leave empty to pick from the user's data (setup until the roles are confirmed, then today's pipeline move, else the week), with a line saying why; setup for the setup trail; today for today's pipeline moves; week for the week ahead |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | The answer, or what was done, in plain words for the user: the same text as content | |
| undo | No | On a saved write: its undo handle, for undo within 24 hours | |
| widget | No | The card the host draws with it, e.g. "pipeline"; "confirm" means a write waits for the user's Yes and nothing is saved yet |