Add an inbond address
Prepares saving an inbond address on the customer's account: a bonded warehouse from list_inbond_warehouses and their bond account number there. If the warehouse is not listed, Cru has to add it first: suggest it with suggest_inbond_warehouse where that tool is available, or ask the customer to email [email protected]. It is never made their default address. This only prepares the instruction: it returns a summary and a confirmation_code and changes nothing until confirm_instruction is called with that code, after the customer agrees.
inbond_address.add, and changes nothing With a connected app’s token, Cru checks the request against live data and either refuses it with a reason or returns a summary and a confirmation code. Nothing happens until confirm_instruction is called with that code — once, within 15 minutes, after the customer says yes.
A partner key is offered this tool opening “Saves” instead of “Prepares saving”. It is carried out at once, with no confirmation step, and takes a required reference as its last argument, so sending the same one again returns the first result. It returns the action’s result as the REST response’s data gives it, with replayed, and is not marked destructiveHint. Partner keys over MCP →
Arguments
2 REQUIRED| ARGUMENT | DESCRIPTION |
|---|---|
| inbond_address_idinteger · ≥ 1 · required | The bonded warehouse, from list_inbond_warehouses. |
| account_numberstring · ≤ 50 chars · required | The customer's bond account number at that warehouse. |
| site_codestring · ≤ 50 chars | Optional: their site code or sub-account there, if the warehouse uses one. |
| nicknamestring · ≤ 50 chars | Optional: the customer's own name for this address. |
Any other argument is refused with a tool error that lists what the tool accepts. Numbers may also be sent as strings, and booleans as "true" or 1.
Returns
STRUCTUREDCONTENTOnce confirmed: inbond_address, as list_inbond_addresses shows it.
The same object also comes as JSON text in content, for hosts that read only that. What a staging tool returns →
Errors
A refusal — a wine that is not on Cru, a price out of range — comes back as a result with isError: true and a message worded for the assistant to act on. A connection without addresses:write is not offered this tool, and calling it anyway returns 403 with a JSON-RPC error naming the scope. Missing or invalid credentials return 401. Conventions every tool shares →