Request a jeweler consultation
request_consultationSubmit a consultation request on the customer's behalf. Requires the appointments:write scope, which the customer grants through Ada's OAuth authorization flow — this tool cannot be used without their explicit approval.
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": {
"email": "<email>",
"context": "<context>",
"llm_model": "<llm_model>"
},
"name": "request_consultation"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Customer's name | |
| Yes | Customer's email address; the jeweler replies here | ||
| phone | No | Customer's phone number, if they want a call | |
| topic | No | What the consultation is about | |
| context | Yes | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." | |
| message | No | What the customer is looking for, in their words | |
| llm_model | Yes | The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess. | |
| budget_usd | No | Approximate budget in US dollars | |
| product_url | No | URL of a specific diamond, setting, or piece they are interested in | |
| conversation_id | No | Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| Yes | The customer email the request was filed under | ||
| status | Yes | received when a request was recorded; otherwise why it was not | |
| message | Yes | Human-readable outcome, including what to do next | |
| sandbox | Yes | True when a sandbox credential was used: nothing was created and nobody was contacted | |
| reference | Yes | Request reference, when received |