Get Compliance Checklist
get_compliance_checklistReturns the company's compliance checklist exactly as the Compliance page of the doola dashboard shows it: the banner, how many tasks sit under each filter, and each task with its due date and status (Overdue, Due soon, Upcoming, Plan ahead or Completed). When checklistStarted is false the user has not set it up yet: never say they are in good standing, tell them to answer the short questionnaire on the Compliance page. When includedInPlan is true doola handles that task as part of their plan. Report statuses as given; the dashboard shows no completion dates. Answer in plain language and never show the user the field names.
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_compliance_checklist"
}
}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. | |
| 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. |