What an account application is missing: blocking items, items needed before recommendations, and recommended items
One command in the Onboarding pack, available in the CLI, as an MCP tool and as a JavaScript import: onboarding gaps.
What it needs, and why
Every input is checked before anything is calculated. application is required; the rest refine the answer.
| Input | Required | The question it asks | Why it matters |
|---|---|---|---|
application | yes | What account type is being opened, and what has been collected so far? | Required records differ for individual, joint, IRA, trust and entity accounts. |
Requests it answers
- “what do we still need to open this account”
- “is this application complete”
- “KYC gaps”
An agent with this pack loaded picks the command from phrasing like that, asks for whatever input is missing, and reports the figures with the method that produced them.
Limits it inherits from wealth-onboarding
ofacStatusmust come from an actual sanctions screen. If it is missing, CIP fails withNOT_SCREENED; never fill it in to make the check pass.- The SSN check validates format only, not issuance or ownership.
- A passing result means the required fields are present and well-formed, not that the applicant's identity is verified.
The full pack, its other 1 command and what it deliberately leaves alone are on the Onboarding page.