# Agents talking to agents: UCP, A2A, NLWeb and WebMCP in plain words

**Canonical URL:** https://teas.co.uk/ai/agents-talking-to-agents/
**Source:** teas.co.uk, UK tea specialist, Tunbridge Wells, Kent

## Shop teas.co.uk from an AI assistant (MCP)

teas.co.uk sells tea, herbal and fruit infusions, hot chocolate and Border biscuits.
MCP server: https://teas.co.uk/mcp (Streamable HTTP), listed in the official MCP Registry as teas.co.uk
Backup address (same server, same tools; use it if /mcp is blocked): https://teas.co.uk/wp-json/teas/v1/shop-mcp
Server card: https://teas.co.uk/.well-known/mcp/server-card.json
Tools: find_products, get_product, compare_products, find_recipes, delivery_and_returns, quote_cart, get_promotions, report_problem, find_substitutes, start_subscription, join_teas, ask_lee, tea_page, search_tea_wiki, read_wiki_article, brand_page, teas_home, browse_shop, browse_recipes, recipe_page, teas_news, read_news, under_the_hood, teas_socials, teas.
Basket: add_to_basket, view_basket, update_basket, checkout_link, checkout_session, basket.
With sign in: get_return_status, get_invoice, get_profile, my_orders, track_order, reorder, my_subscriptions, change_subscription, rewards_balance, start_return, my_account.
No sign in is needed to search, compare, build a basket or get a checkout link. The person always pays on teas.co.uk.
Cards: in assistants that draw MCP Apps cards, products, comparisons, the basket, checkout, orders, repeat deliveries (pause, resume, cancel), reward points and returns appear as cards.
Every assistant except ChatGPT, until OpenAI approves the next version: quote_cart, get_promotions, get_return_status, get_invoice, report_problem, find_substitutes, start_subscription, join_teas, ask_lee, tea_page, search_tea_wiki, read_wiki_article, brand_page, teas_home, browse_shop, browse_recipes, recipe_page, teas_news, read_news, under_the_hood, teas_socials, teas, basket, my_account.
Set up guides: https://teas.co.uk/ai/

## Summary

Shopping agents can search our teas, ask our tea agent Nicola and make a buy link. They never pay: you always pay on teas.co.uk.

## Description

More and more, the thing visiting a shop isn't a person. It's software working for a person. Some of it is an AI assistant. Some of it is a shopping agent built by a big company. Some of it is another AI agent passing a job along. I want all of them to find the right tea and hand the person a fair choice. So teas.co.uk speaks four of the open standards they use.
When a robot does the shopping, it buys from the shop it can understand.
UCP: a shopping standard for big shopping agents
UCP (Universal Commerce Protocol) is a shared way for shopping agents, the kind Google and Microsoft build, to talk to shops. Our UCP profile is at teas.co.uk/.well-known/ucp. It lets an agent:
search the cataloguelook up one tea in detailmake a buy link
It deliberately lists no payment method. The agent can find the tea and make the link. The person opens it and pays on teas.co.uk.
A2A: our tea agent, Nicola
A2A (agent to agent) is a standard for AI agents to talk to each other. Ours is called Nicola, the teas.co.uk tea assistant. Its card is at teas.co.uk/.well-known/agent-card.json and it lists three skills:
Tea advice in plain words.Find products, with live prices and stock.Basket link, for the person to open.
Nicola never pays and never places an order.
NLWeb: ask the shop a whole question
NLWeb is a way for software to ask a website a question in ordinary language. Send teas.co.uk/ask a question like "which tea goes best with digestives?" and it answers with the teas that fit. Like all our question doors, it is read only: asking changes nothing.
WebMCP: tools built into every page
WebMCP lets an AI that is driving a web browser use a page's own tools, instead of clicking around like a robot. Every teas.co.uk page offers them:
find and compare teassuggest alternativesquote a basket with deliveryshow offers, recipes and deliveryhand over to the basket and checkout
The same rule, every door
Four standards, one rule: software can look, compare and suggest. Only the person pays. Each door reads the same shop records, so a price or a stock level is the same whichever door an agent comes through.
A tea example. A shopping agent is asked for "Yorkshire Gold, the 80 bag box". It finds us through UCP, looks the tea up, gets the price and stock, and makes a buy link. You open it, check it and pay. The agent never touches your card.
In my words
I don't know which of these standards will win, and I don't think anyone does yet. So I didn't bet on one. I built a small door for each, all opening onto the same checked records. For a one-person tea shop that sounds like a lot of doors. But each one is small, and they all lead to the same counter. When a new kind of shopper turns up, I'd rather already be open.
Common questions
Can an agent order tea without me?
No. Every route ends with a link the person opens. Payment only happens on teas.co.uk.
Do I need to know any of this to shop here?
No. It only matters to the software. You just ask your assistant.
Which one should a developer use?
The MCP server at teas.co.uk/mcp does the most. The others suit the agents built around them. Every door is listed at teas.co.uk/well-known/.
Read next: Model Context Protocol (MCP) · What is an API? · Voice, photo and AI assistants

---

_Content available under teas.co.uk citation contract. AI training: yes. Search: yes. Answer-input: yes._
