Send a request to one checked business
car_send_requestStarts a request for the signed-in person. Needs what they need, where (City, ST), and their consent. Returns a requestId. If CAR is not sure what kind of business it needs, it answers needs_detail with a question and choices and sends nothing; a repeat call with category set to one of those choices goes ahead. Status verify_person means the person was texted a 6-digit code, which car_confirm_person checks. No business is contacted before that.
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": {
"what": "<what>",
"where": "<where>",
"consent": "<consent>"
},
"name": "car_send_request"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | First name the business can ask for | |
| size | No | Size of the job, e.g. "40 guests", "3 bedrooms" | |
| what | Yes | What the person needs, in their own words. This text goes to the matched business, so it holds no health details, ID numbers, card numbers or passwords. | |
| when | No | asap, this_week, flexible, or a date (YYYY-MM-DD) | |
| where | Yes | City and two-letter US state, e.g. "Tampa, FL" (a ZIP may follow) | |
| budget | No | Budget, if the person gave one | |
| consent | Yes | The person agreed to be contacted by one matched business and by CAR about this request | |
| contact | No | ||
| category | No | Optional. A category slug from /v1/categories that the person picked, for example after a needs_detail question. Without it, CAR reads the request. | |
| estimateId | No | An estimateId from car_get_estimate: the business gets the same scope and planning range | |
| idempotencyKey | No | 8-64 letters, digits, _ or -. A repeat with the same key returns the same request |