Current reference · Technology
Inside Diamond Scout’s agent-ready search
IZIOS is preparing a read-only Diamond Scout MCP rollout so assistant developers can understand bounded discovery tools before any remote access is approved.
- Source context
- Published October 21, 2026
- IZIOS review

Diamond Scout began with a simple use case: someone knows roughly what they want, but not how to turn that into a useful diamond search. They may ask for an oval laboratory-grown diamond around a certain budget, or say that they want a blue stone with a particular shape. A good assistant can turn that sentence into a focused request, return a small group of public listing links, and explain why those options fit the words used. The person still sees the individual diamonds rather than receiving a mysterious recommendation with no path back to the source.
From a question to listing links
MCP, short for Model Context Protocol, gives software assistants a shared way to discover and call tools. A tool has a name, a purpose, and a defined input; its reply can carry information an assistant can use in a conversation. For Diamond Scout, that makes the handoff easy to picture. An assistant could pass along a request such as an oval laboratory-grown diamond below a stated budget, then present the returned listing links and point the shopper to the report and media for the finalists. The useful moment is not the protocol itself. It is getting from a natural question to material a person can inspect.
Three remote tools, five browser tools
The prepared remote tool set has three jobs. ask_diamond_scout handles a buyer's natural-language search. get_diamond_answer provides reviewed education by topic, useful when a shopper asks what a term means before narrowing a search. get_metals_data_access points to public metals-data documentation and the relevant reference material; it does not pretend to be a new spot-price quote. Keeping those functions distinct makes a conversation easier to follow. A search result is a search result, an educational answer is an educational answer, and a metals reference is a reference.
There is a second, browser-facing path with five tools for Scout search, catalog search, diamond details, comparison, and recommendations. That browser experience is separate from the three-tool remote MCP preparation. Both are designed around discovery rather than checkout. The five browser tools are useful when a person is already looking at the site and wants to move between a broad search, a single diamond, and a side-by-side comparison. The remote shape is for a developer planning how an external assistant might make the same kind of read-only handoff.
What is being prepared
Remote MCP access is being readied for approved developer rollout. The published guide describes the intended workflow; credentials and partner-specific access still need to be confirmed when a connection is offered. For example, an application could keep the returned listing links beside the original question, so someone can revisit the shortlist and see which criteria produced it. The current listing remains the place to check availability and the details of the individual diamond before checkout.
A useful handoff leaves the person with something they can examine. They can open a report, compare two outlines or refine a budget and search again. For a developer, the small tool set makes those steps explicit. For the shopper, the protocol can stay in the background while the conversation moves from a broad idea toward a particular stone.