What an application needs
get_application_checklistWhat an application form will ask for, before helping with one: which facts the candidate's résumé already has on file (name, email, phone, location, a profile link, work history, education), which are missing and how to add them (fix_in_chat first, fix_url for the website), the questions still to ask the candidate because neither the résumé nor their saved answers settle them (work authorization, salary, start date), and what only their computer has. For the résumé it says whether a fact is on file, not the fact: get_resume has the document. A connection that may also update the profile gets saved_answers too, the answers the candidate saved with update_application_answers, and setup: whether the answers every form needs are there (where they may work), each gap with the question to ask word for word and its options, the postal-address answers still open (address_missing, asked only when a form asks for the address), and prefill, what the résumé already says, to put to the candidate as a yes. Ask those only when the candidate starts applying (prepare_application lists them then), not when they connect or search, and save them with update_application_answers. Nothing is stored and nothing goes to an employer.
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_application_checklist"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||