ippodotea.com WebMCP audit

audited Aug 28, 2026in 6s
64/ 100

16 tools registered. Strongest in usefulness, weakest in human experience.

WebMCP use71
Usefulness95
Human experience0
about:blank

No agent run recorded yet.

No steps recorded

Tools

/
ippodo_recommend_tea: warning

ippodo_recommend_tea

Use when a shopper wants Ippodo tea recommendations based on taste, caffeine, brewing style, experience, gift intent, time of day, or tea category rather than a product name. Ranks the live tea-quiz assortment of matcha, gyokuro, sencha, bancha, and teabags, returning in-stock products with match reasons and the cheapest available variant. Prefer this over search_catalog for preference-based discovery such as a first latte, caffeine-free evening tea, or first-time matcha. After the shopper chooses a tea, call get_product for variants, ippodo_get_brewing_guide for preparation, or ippodo_build_tea_setup for utensils, then Shopify update_cart to add items. Leaves the cart unchanged.Answers a question. Declared read only.
pagehttps://ippodotea.com/
implementation
viaimperative
entry pointdocument
registered after421ms
executepresent
api surface
categoryoptional
occasionoptional
formatoptional
flavoroptional
caffeineoptional
preparationoptional
experienceoptional
giftoptional
limitoptional
annotations
read onlytrue
destructivefalse
idempotenttrue
open worldfalse
untrusted contentnot declared
titlenot declared
2 findings
warningSchema quality
1.5 / 4
10 of 16 tool schemas are harder for an agent to use than they need to be: ippodo_recommend_tea description is 688 characters, over Chrome's 500-character guidance.
ippodo_recommend_tea: description is 688 characters, over Chrome's 500-character guidance; ippodo_recommend_tea: 6 parameter descriptions are over Chrome's 150-character guidance; ippodo_get_brewing_g
fix
{
  name: "ippodo_recommend_tea",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}
warningHuman parity
0 / 8
16 of 16 tools run through the JavaScript API with no visible counterpart, so the person co-browsing cannot see what the agent is offered. Declarative forms (or at least a title annotation) close the gap.
ippodo_recommend_tea, ippodo_get_brewing_guide, ippodo_build_tea_setup, ippodo_compare_teas, ippodo_get_subscription_options
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="ippodo_recommend_tea" tooldescription="...">
  <!-- the same action, as UI -->
</form>
tool json
{
  "name": "ippodo_recommend_tea",
  "description": "Use when a shopper wants Ippodo tea recommendations based on taste, caffeine, brewing style, experience, gift intent, time of day, or tea category rather than a product name. Ranks the live tea-quiz assortment of matcha, gyokuro, sencha, bancha, and teabags, returning in-stock products with match reasons and the cheapest available variant. Prefer this over search_catalog for preference-based discovery such as a first latte, caffeine-free evening tea, or first-time matcha. After the shopper chooses a tea, call get_product for variants, ippodo_get_brewing_guide for preparation, or ippodo_build_tea_setup for utensils, then Shopify update_cart to add items. Leaves the cart unchanged.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "category": {
        "type": "string",
        "enum": [
          "any",
          "matcha",
          "gyokuro",
          "sencha",
          "bancha",
          "teabags"
        ],
        "description": "Tea family to keep in the result set. Use \"matcha\", \"gyokuro\", \"sencha\", \"bancha\", or \"teabags\" when the shopper named a category. Use \"any\" when they did not. Matched against product handle, title, and type — not tags or description boilerplate."
      },
      "occasion": {
        "type": "string",
        "enum": [
          "morning",
          "daytime",
          "teatime",
          "evening",
          "after_meal"
        ],
        "description": "When the shopper plans to drink the tea. Evening and after_meal boost lower-caffeine and roasted options; morning and daytime prefer brighter or standard-caffeine teas."
      },
      "format": {
        "type": "string",
        "enum": [
          "matcha",
          "loose_leaf",
          "teabags",
          "any"
        ],
        "description": "How the shopper wants to prepare tea. \"matcha\" keeps powdered teas, \"loose_leaf\" keeps leaf teas, \"teabags\" keeps bagged teas, and \"any\" does not filter by format."
      },
      "flavor": {
        "type": "string",
        "enum": [
          "umami",
          "balanced",
          "fresh",
          "sweet",
          "roasted",
          "smoky",
          "any"
        ],
        "description": "Dominant flavor the shopper asked for. \"umami\" and \"balanced\" favor classic matcha and gyokuro; \"roasted\" and \"smoky\" favor hojicha and similar; \"any\" skips flavor ranking."
      },
      "caffeine": {
        "type": "string",
        "enum": [
          "standard",
          "low",
          "none",
          "any"
        ],
        "description": "Caffeine preference. \"none\" returns only caffeine-free teas such as mugicha; \"low\" boosts hojicha, genmaicha, and mugicha; \"standard\" keeps typical green-tea caffeine; \"any\" does not filter."
      },
      "preparation": {
        "type": "string",
        "enum": [
          "usucha",
          "koicha",
          "latte",
          "standard",
          "hot",
          "iced",
          "cold_brew",
          "any"
        ],
        "description": "Brewing or serving style. \"latte\" boosts Ikuyo and similar culinary matcha; \"koicha\" boosts thicker usucha/koicha grades; \"usucha\" favors everyday whisking matcha; \"cold_brew\" and \"iced\" favor teas that drink well chilled."
      },
      "experience": {
        "type": "string",
        "enum": [
          "first_time",
          "experienced"
        ],
        "description": "Shopper familiarity. \"first_time\" boosts approachable daily teas such as Sayaka and Ikuyo; \"experienced\" leaves room for richer grades such as Ummon."
      },
      "gift": {
        "type": "boolean",
        "description": "Set true when the purchase is a gift. Boosts giftable cans, classic matcha, and the Ippodo gift card."
      },
      "limit": {
        "type": "integer",
        "minimum": 1,
        "maximum": 5,
        "default": 3,
        "description": "Maximum number of teas to return. Defaults to 3. Use 5 only when the shopper wants a wider shortlist."
      }
    },
    "required": [],
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true,
    "destructiveHint": false,
    "idempotentHint": true,
    "openWorldHint": false
  }
}
Showing ippodo_recommend_tea

Findings

WebMCP use

71 / 100 · weight 50
passTools registered
4 / 4
16 tools registered across 1 page.
failReal-browser eligible
0 / 8
The page's code registers these tools, but a real visitor's browser does not get them yet: WebMCP needs a native modelContext or a current origin trial token, and this page has neither. The page does carry an origin-trial token, but it does not grant WebMCP on this origin.
passRegistration timing
4 / 4
Every measured tool registered within 491.2999999523163ms of navigation.
toolshow_variant
passCanonical entry point
4 / 4
All 16 tools register on the canonical document.modelContext entry point.
passSchema validity
5 / 5
All 16 tools declare a structurally valid object input schema.
warningSchema quality
1.5 / 4
10 of 16 tool schemas are harder for an agent to use than they need to be: ippodo_recommend_tea description is 688 characters, over Chrome's 500-character guidance.
toolippodo_recommend_tea
ippodo_recommend_tea: description is 688 characters, over Chrome's 500-character guidance; ippodo_recommend_tea: 6 parameter descriptions are over Chrome's 150-character guidance; ippodo_get_brewing_g
fix
{
  name: "ippodo_recommend_tea",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}
passStub detection
5 / 5
All 16 tools declare an execute handler.
passAnnotations present
4 / 4
All 16 tools declare a readOnlyHint, so an agent knows which calls change state.
passAnnotation mismatch
3 / 3
No tool claims to be read-only while its name says it writes (16 declared hints checked).
warningUntrusted content hint
0 / 2
1 of 1 tools look like they return text written by other people but declare no untrustedContentHint, so an agent will treat the response as the site speaking.
toolmanage_orders
manage_orders: user, customer
fix
{ name: "manage_orders", annotations: { untrustedContentHint: true } }
passRegistration errors
2 / 2
No tool registration threw during the capture.
warningToolchange coherence
1 / 2
16 tools were registered but the page never dispatched a toolchange event, so an agent subscribed to registry updates never learns they exist.
fix
document.modelContext.dispatchEvent(new Event("toolchange"));
not applicableInjection surface
0 / 3
The injection-surface model hop returned no usable result, so tool contracts were not reviewed for injection surface.

Usefulness

95 / 100 · weight 30
warningNaming quality
1.5 / 2
Tool naming makes selection harder than it needs to be: 1 name is over Chrome's 30-character guidance; 8 names do not start with a verb (ippodo_recommend_tea).
toolippodo_get_subscription_options
fix
{ name: "ippodo_get_subscription_options" /* short, unique, verb-based */ }
not applicableDescription quality
0 / 6
The description-quality model hop returned no usable result, so descriptions were not rated.
not applicableTool selection
0 / 14
The tool-selection model hop returned no usable result.
passCoverage vs. site type
8 / 8
The tool set covers the whole core commerce flow: search or browse the catalog, read one item in detail, add to or read the cart, start checkout or place an order.

Human experience

0 / 100 · weight 20
warningHuman parity
0 / 8
16 of 16 tools run through the JavaScript API with no visible counterpart, so the person co-browsing cannot see what the agent is offered. Declarative forms (or at least a title annotation) close the gap.
toolippodo_recommend_tea
ippodo_recommend_tea, ippodo_get_brewing_guide, ippodo_build_tea_setup, ippodo_compare_teas, ippodo_get_subscription_options
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="ippodo_recommend_tea" tooldescription="...">
  <!-- the same action, as UI -->
</form>
not applicablePage experience
0 / 12
The page-experience model hop returned no usable result, so the page was not graded.

Tool selection

The tool-selection model hop returned no usable result.
how this was captured
chrome
148.0.7778.96
capture shim
v1
spec snapshot
2026-08
mode
fast
pages
1
tools
16
run time
6s
finished
Aug 28, 2026