Tool inspector
Inspect lets you browse a store's tools and call them yourself, one at a time, with no model in the loop. It is the quickest way to learn what a store supports before you start a run.
Signed in, it lives at Inspect, and every call you send is kept as an Inspect session in History. Without an account, the public Inspector does the same job; it is described at the end of this page.
Starting an Inspect session
- Open Inspect and answer Which store?: type a domain or pick a test store (Flowers, Stays or Food), then Continue.
- Inspect asks How do you want to inspect the store, and offers three views:
- Steps: the store's UCP flow in order, each step with its tools. Read what the store published and try each tool in turn.
- Tools: every tool the store lists, with a form built from its own schema, or JSON. For exact calls.
- Store: search, add to cart, check out and look up orders, as a buyer would (for a Stays store: search stays, book a room and rate, add the booker). Each button is one call.
- Choose what Calls go over: the transports the store declares (MCP, REST, and A2A when it offers a store agent, with its version) and WebMCP, the store's website. A store with no MCP service is inspected over REST: that is the only UCP transport offered, and no MCP request is sent to it.
- Click Start. Inspect reads the store's discovery, records it, and opens the session.
While you choose, the Info pane on the right shows what the store publishes: its UCP profile and release, kind of store, environment, transports, capabilities and account linking. You can switch view and transport at any time in the session.
Browsing tools
Inspect lists the store's tools (over MCP, with a tools/list call). Each tool has:
- Name: the identifier used in calls, such as
search_catalogorcreate_cart. - Description: what the tool does and when to use it, in the store's words.
- Input schema: the JSON Schema for its parameters, with types and which are required.
The schema tells you exactly what a tool accepts. For example, a checkout tool might require an idempotency-key as a UUID, while a search tool might accept optional filters and pagination objects.
Calling tools
Pick a tool and fill in its arguments in one of two forms: Visual (a form built from the tool's schema) or JSON (the arguments as one JSON object). Click Send. Calls are sent signed, with the UCP-Agent profile, from our cloud. Over MCP, Inspect sends a tools/call request, here to Shopify's storefront search tool:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "search_shop_catalog",
"arguments": {
"query": "blue running shoes",
"limit": 5
}
}
} On complete_checkout and cancel_checkout, Inspect adds the idempotency key for you, a new one on each Send. To retry the same attempt, put your own meta["idempotency-key"] in the arguments; it is kept.
The result has three tabs: Request, Response and Timing. Readable unfolds JSON held inside strings; As received shows the exact bytes. Choose a past call to load it again with Edit and send again. If a call fails, the error is shown with a link to report it.
The pane on the right is the same as a run's: Trace (every call kept whole, secrets shown as prefixes), Discovery and negotiation and Info.
Common UCP tools
Most UCP stores implement a standard set of tools for the whole shopping flow:
- search_catalog (Shopify's older storefront endpoint:
search_shop_catalog): search products by keyword, filters and pagination. Returns product summaries with prices and availability. - lookup_catalog: look up several products or variants by id in one call. Ids the store does not know are left out, and the store may say which.
- get_product: one product in full, including variants, options, images and stock.
- create_cart: start a cart with one or more line items. Returns a cart ID for later calls.
- update_cart: add, remove or change quantities in an existing cart.
- create_checkout: start a checkout from a cart. Returns the checkout with totals, shipping options and required fields.
- complete_checkout: finish the checkout with payment and buyer details to place the order.
Some stores add tools such as get_cart, cancel_cart, get_checkout, update_checkout and cancel_checkout for finer control.
Stays stores
A store that declares the dev.ucp.lodging service (the draft lodging booking capability, dev.ucp.lodging.booking) is a Stays store. Its Store view is a booking flow instead of a product search: Search stays, pick a room and rate, add the Booker, and Book this stay. It works over MCP and REST.
The booking shows exactly what the store returned: its status, the price breakdown (totals), when each amount is paid (payment.terms: due today, later, or at the property), the cancellation policy and its refundability, and the store's messages. Errors say what the store still needs, such as the booker; disclosures, such as a local tax, are shown in full. A held room can be released with Release the hold.
Stores with no MCP service
MCP is one of UCP's transports, not a required one. When a store's profile lists a REST service and no MCP service, Inspect starts the session over REST. There is no tool list to ask a REST store for, so the tools are the operations of the capabilities its profile declares, under the names the MCP binding uses: search_catalog, lookup_catalog, get_product, the cart and checkout operations with their cancels, get_order, and location search and lookup when declared. Steps, Tools and Store all work, and each call is shown in the trace as the REST request that was sent. See REST API transport. To try one, inspect flowers-rest.ucpsandbox.com.
Account linking
When a store's profile declares dev.ucp.common.identity_linking, the Store view shows an Account card with Link an account. The sign-in server is found the way UCP 2026-08-25 describes: the protected-resource metadata on the business domain (the host whose profile was read), then the authorization server it names, or the business domain itself when there is no such document. The host a service endpoint is on plays no part, so a store whose REST and MCP services are on a shared API host links like any other. Once linked, every call of the session carries the buyer's token, over MCP and REST alike, and the trace shows it cut to a prefix. To try a store with its endpoints on another host, inspect flowers-account-split.ucpsandbox.com.
Shopping permalinks
A store that declares dev.ucp.shopping.permalink (UCP 2026-08-25) gets an open_permalink tool under Checkout, marked LINK. A permalink is a browser link that opens the store with the named items ready for the buyer; it is not an MCP or REST call, so the tool is the same on every transport. Give it items (id and quantity) and, if you like, a continue_to path, buyer details, discount codes, context or attribution. Inspect then:
- writes the link on the store's declared endpoint as the spec describes:
/buy/sku_123:2,sku_456:1, an id outside letters, digits,.,_and-as~plus base64url, and fields as paths such asdiscounts/codes/0=SAVE10; - opens it once, as a browser would, unsigned, without following the redirect;
- reports the destination and whether the store answered as the capability requires:
303 See Other(never301or308), aLocation,Cache-Control: no-store, a referrer policy, and no UCP JSON.
Opening a permalink never places an order or takes payment: the buyer finishes at the destination. A rule the store misses is shown in the result, not as a failed call. To try one, inspect flowers-permalink.ucpsandbox.com.
The store's website (WebMCP)
Choosing WebMCP as the transport opens the store in our browser and lists the tools its own web page registers. That is not a UCP transport. If the website offers none, Inspect says so. See WebMCP: the store page.
The store agent (A2A)
On a store that offers a store agent, choose A2A and its version. Checkout actions go to the store agent as messages; search and product lookup go over MCP. Each action has a form, the payment travels as its own part on complete_checkout, and the headers that turn A2A and UCP on are shown and can be switched off. See A2A: the store's agent.
The store's checkout (Embedded)
On a store that lists Embedded, the Hand-off step has open embedded checkout. Create a checkout first; when its answer carries the embedded binding, Inspect loads the store's page with the delegations you tick and logs every message. See Embedded: the store's checkout.
The public Inspector
The public Inspector needs no account. Enter a domain, or use one of its test-store pills (flower-shop.local for shopping, hotel.local for lodging, both hosted by the Playground). Buttons above the results switch between the transports the store declares: MCP lists the tools and lets you call them, REST gives you a search, product cards and a cart. WEBMCP shows the store page's own tools beside its UCP tools.
Its rail carries four panels:
- Health Check: a letter grade for the store's UCP profile and a passing-checks ratio (for example
9/11), with each check marked pass, warn or fail. The checks cover profile structure: version format, declared services and their transport endpoints, capabilities and their versions, reverse-domain naming, payment handlers and signing keys. Warns count half toward the grade. Tool schema grading is separate; see Schema Quality. - Buyer context: the spec's provisional buyer signals (
address_country,address_region,postal_code,language,currency). Set them once (the pill opens an inline editor; Settings holds the lasting copy) and every catalog search carries them where the store's tool accepts them: insidecatalog.contexton the Shopify-shapedsearch_catalog, as a top-levelcontextobject where a tool's schema declares one, and on the RESTPOST /catalog/search. They are hints for localisation, not identity. Some stores answer in local currency; others ignore the hint. - Held state: what stores are holding for you. When a call creates or updates a cart, opens a checkout or holds an offer, the store's answer is mirrored into one row per store and kind, with its totals, line items, continue link, expiry and any warnings. A countdown runs from the store's
expires_at; an expired hold or a failed call marks the row stale. Forget drops our copy only and never contacts the store. - Negotiation: the connect handshake in five steps: discover the profile, select a version, intersect the declared capabilities with the ones the Playground supports, resolve extension blocks, and choose the prompt variant. Every capability row is marked active, passthrough or excluded, with a reason.
Its hotel.local test store takes test cards (tok_visa approves, tok_decline declines). Discovery is outside the lodging capability, so hotel.local provides its own search_properties tool and labels it as not part of UCP.
The same thing, headless
Everything Inspect does is also three API calls, gated by the inspect token ability:
POST /api/v1/inspect/discover: resolve a domain's UCP profile to endpoints and capabilities, with the same negotiation readoutPOST /api/v1/inspect/tools: list an endpoint's tools with their schema-quality gradePOST /api/v1/inspect/call: call one tool by hand and get the raw result
See the API Reference for request shapes and examples.
Inspect a store before you run an agent on it. Knowing which parameters are required and what the responses look like makes it much easier to judge what the agent did.
Something wrong on this page?