Switch Active Company
switch_active_companyPoint the formation tools at a different company the customer already owns. Use when the customer asks to manage / continue / inspect a specific company by name or ID. The companyId must come from list_companies — unknown IDs are rejected. After switching, the response carries the same shape as get_company_onboarding_status for the new active company, so the agent knows immediately which step to resume from. The override is process-local; if the customer reconnects and ends up on a different MCP replica, just call this tool again.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"companyId": "<companyId>"
},
"name": "switch_active_company"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| context | No | Optional, for analytics only. In one sentence, why you are calling this tool and how it serves the user's goal. Describe the purpose in general terms: never include names, emails, phone numbers, addresses, IDs or any other personal details. | |
| companyId | Yes | Target companyId — must be one of the IDs returned by list_companies for this customer. | |
| llm_model | No | Optional, for analytics only. Your exact model identifier from your system prompt (e.g. "claude-opus-4-8"), or "unknown" if unsure. Never guess. | |
| conversation_id | No | Optional, for analytics only. The exact conversation_id from this server's previous response, unchanged. The first response provides one, so leave this out until you have it and never invent one. Keep passing the same value for the rest of the conversation, even when the user moves on to a new request. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| No | Customer email | ||
| error | No | true if an error occurred | |
| message | No | Human-readable status | |
| blockers | No | Prerequisites still unmet, in flow order. Same vocabulary as the `missing` array submit_for_review returns. Empty array when formation is fully complete. | |
| lastName | No | Customer last name | |
| nextStep | No | The step the formation flow now waits on; null once formation is complete. | |
| companyId | No | Customer's active formation company ID, if any | |
| firstName | No | Customer first name | |
| customerId | No | Customer ID from the OAuth bearer | |
| dashboardUrl | No | URL to doola dashboard | |
| nextQuestion | No | The customer-facing question for nextStep; null once formation is complete. | |
| completedSteps | No | List of steps inferred as completed from the Company / Customer state | |
| conversation_id | No | This conversation's handle. Pass it unchanged as conversation_id on every later call. | |
| hasActiveSession | No | false if the request was not authenticated (defense in depth) | |
| suggestedNextStep | No | The tool for the step the flow waits on, as in nextStep; null when formation is complete. | |
| countryOfResidence | No | ISO Alpha-3 country code if set | |
| responsiblePartySsnOnFile | No | Whether doola has the responsible party's SSN for the EIN application. Only ever this boolean: no tool returns the SSN or any part of it. |