soclasica_get_order_status

What it does

soclasica_get_order_status returns the current state of a single Soclasica order. Soclasica is the beauty site at soclasica.com: makeup, skincare and beauty tools, with tracked delivery to 38 countries. You pass one order number and the tool answers with the order number, its status, how many items are in it, the total in cents, the currency, and a tracking list.

It is a Read tool, so it changes nothing on the account. It is also idempotent: call it twice with the same order number and you get the same answer, which makes it safe to retry after a network drop or to poll while a parcel moves.

When an assistant should call it

Call it when someone asks where their Soclasica order is, whether it has shipped, or what carrier and tracking number to look up. It is the follow-up to soclasica_list_my_orders: that tool gives the order numbers, and this one goes deep on whichever order the person names.

It also fits the common support conversation where a person quotes an order number and asks for a plain-language status. The assistant reads status and the tracking entries and explains them, without touching the order.

Do not reach for it when the person has no order number yet; start with soclasica_list_my_orders. Do not use it for product questions either, since soclasica_search_products and soclasica_gift_ideas cover those.

Inputs and an example call

One input: order_number, required, a string of up to 80 characters. It is the order number as Soclasica issued it, for example the value returned by soclasica_list_my_orders. Nothing else is accepted, no email address, no partial match.

The call goes to the account connector at https://onelifevibe.com/mcp as a tools/call with the name soclasica_get_order_status:

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"soclasica_get_order_status","arguments":{"order_number":"<order_number from soclasica_list_my_orders>"}}}

That connector needs the person's OneLifeVibe sign-in (OAuth 2.1 with PKCE) and the scope olv.read. The person must also have signed in to soclasica.com with OneLifeVibe at least once; without that link, the tool answers not_linked. The connector's sign-in is set up for Meta Muse today (client onelifevibe-muse), and other MCP clients reach the no-account tools through the free connector.

What comes back

The result carries the order number, its status, items_count, the total as total_cents plus currency, and a tracking array. Each tracking entry has carrier, number, url and status, so the assistant can name the carrier, read out the tracking number, link to the tracking page and describe that leg's own status.

Treat number, status and the tracking fields as the source of truth and read them back as they arrive, including currency: total_cents is an integer in the smallest unit of that currency, so 1299 in USD is 12.99. An order can have more than one tracking entry, so loop over the array rather than reading only the first element.

On the Platform API, soclasica_get_order_status is listed in GET /api/platform/v1/tools, but a platform key gets 501 world_tools_unavailable for it today, because it acts on one member's own data. A platform key can still call the world catalogue, the tool registry, the network directory tool and the event log.

Errors, limits and safety

not_linked means the person has not yet signed in to soclasica.com with OneLifeVibe. Send them to soclasica.com to sign in once, then retry. A missing required input or a credential problem is answered the same way as for other connector tools: fix the argument or finish the OAuth 2.1 with PKCE sign-in and the olv.read scope, then repeat the call. Because the tool is idempotent, retrying is safe.

501 world_tools_unavailable will appear if you try this tool with a platform key. That is not a transient error; route the request through the account connector instead, or use the platform key for the catalogue, registry, directory and event log tools.

There is nothing to confirm before calling, since the tool only reads. Keep order numbers out of shared logs where you can, pass the order number exactly as issued, and stay within 80 characters. An assistant should never guess an order number to probe for a match; ask the person, or list their orders first.