Resolve gap
crm_resolve_gapTurn a gap into a named contact — with full provenance. The only way a gap becomes named (CRM-2), and it demands the same provenance as a fresh contact — the gap does not lower the bar. The gap_note stays on the row: what we did not know is part of how we came to know it. Effects: contact gap -> named.
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": {
"contact_id": "<contact_id>",
"name": "<name>",
"source": "<source>"
},
"name": "crm_resolve_gap"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | The person. | |
| No | As publicly listed or personally shared, if the source includes one. | ||
| phone | No | Same rule as email. | |
| title | No | Their title, as the source states it. | |
| source | Yes | Where the name comes from (CRM-1). | |
| contact_id | Yes | The gap row, e.g. P-0002. | |
| linkedin_url | No | The person's public LinkedIn profile URL, if the source includes one. | |
| confidence_note | No | How sure, and of what. |