Skip to main content
Glama

Kapruka MCP

by com.kapruka
OverviewDiscussionsAdmin

Server Details

Free public MCP server for Kapruka.com — Sri Lanka's largest e-commerce platform.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over 55 days
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
kapruka/mcp
GitHub Stars
21
Server Listing
Kapruka MCP Server

TDQS

A4.6/5.0

Scored across 8 tools

Disambiguation5/5

Each tool targets a distinct resource/action: delivery cities listing, delivery feasibility check, product search, product fetch, category listing, order creation, order tracking, and options-card rendering. No two tools overlap enough to cause misselection.

Naming Consistency5/5

All eight tools use the same kapruka_ prefix and consistent snake_case verb_noun pattern (check_delivery, create_order, get_product, list_categories, list_delivery_cities, render_options_card, search_products, track_order). Fully predictable and readable.

Tool Count5/5

Eight tools is well-scoped for a chat-commerce concierge: discovery, delivery validation, ordering, and post-order tracking. No tool appears redundant or out of place.

Completeness3/5

Core browse-to-order-to-track lifecycle is covered, but kapruka_create_order repeatedly references kapruka_custom_cake_status and kapruka_custom_cake_request, neither of which exists in the tool set. That leaves the custom-cake workflow a dead end, and there is no order cancellation or modification tool.

Available Tools

8 tools
kapruka_check_deliveryA
Read-only
Inspect

Check whether Kapruka can deliver to a given city on a given date, and the delivery fee.

Returns whether the requested date is available (if not, the next available
date plus reason) and the delivery fee the checkout will charge.

THE FEE DEPENDS ON THE CART AND THE CURRENCY — the city's base rate is not
what checkout charges. Sri Lankan customers (LKR) pay the city rate capped
by the cart value (25% of the item value, at least LKR 300; some remote
cities 50%), so a small cart to a far city pays far less than the rate.
Overseas customers (USD) pay a fixed USD fee per city, whatever the cart.
Pass `currency` and the `cart` you are about to order and the answer gives
the EXACT fee kapruka_create_order will charge ("Delivery fee for this
cart"). Without a cart, an LKR answer gives only the MOST the fee can be
("up to"). One shipment per order: the fee covers the whole cart.

Pass `product_id` whenever the customer has named a product: the answer then
also checks that ITEM's delivery scope (restaurant food, hotel cakes and
liquor only reach selected cities, typically the Colombo area). With a
product_id, `available` is true only if the date is open AND the item is
deliverable to that city. When `item_deliverable` is false, offer the
customer one of the returned `deliverable_cities` or an island-wide
alternative — do not attempt kapruka_create_order with the same city, it
will be rejected. An unknown product_id is silently ignored (no item fields
in the result), so check `item_deliverable` is present before relying on it.

product_id also selects the SAME-DAY rule the checkout applies to that item:
vendor-delivered items (restaurant food) can go today until late afternoon;
ordinary items move to the next date; ordinary same-day is only possible early
in the morning near Colombo. So a check without product_id can differ from one
with it — always pass it once an item is chosen. When `available` is false,
offer `next_available_date`. Do not interpret the `reason` text (it is the
website's wording and may say slots are full when the real cause is the cutoff).

Perishable codes (CAKE*, FLOWER*, COMBO*) additionally get a freshness
warning when the chosen delivery date is more than 1 day out.

Args:
    params (CheckDeliveryInput):
        - city (str): Canonical city name (e.g. 'Colombo 03', 'Galle')
        - delivery_date (Optional[str]): YYYY-MM-DD; defaults to today (LK time)
        - product_id (Optional[str]): Check the city against this item's delivery scope
        - currency (Optional[str]): LKR (default) or USD/GBP/AUD/EUR (charged in USD)
        - cart (Optional[list]): [{product_id, quantity, icing_text?}] for the exact fee
        - other_items_total (Optional[float]): LKR value of items not in `cart` (custom cake quote)
        - response_format (str): 'markdown' (default) or 'json'

Returns:
    str: Delivery feasibility + fee in the requested format.

    JSON schema:
    {
      "city": str,
      "now": str,                       # ISO timestamp, Sri Lanka time
      "checked_date": str,              # YYYY-MM-DD
      "available": bool,                # date open AND (if product_id) item deliverable
      "delivery_fee": number,           # what checkout charges (see fee_basis)
      "fee_currency": "LKR" | "USD",
      "fee_basis": "cart" | "max" | "fixed",  # exact for the cart | LKR without a cart: the most it can be | USD: same for any cart
      "fee_items_value": number,        # LKR item value the fee was computed from (fee_basis=cart)
      "fee_cart_error": str,            # the cart could not be priced (fee falls back to max)
      "rate": number,                   # the city's BASE rate (LKR) — not the checkout fee
      "currency": "LKR",
      "reason": str | null,             # date-block message, else "This item is not delivered to <City>."
      "next_available_date": str|null,  # only for date blocks
      "item_deliverable": bool,         # only when product_id resolved to a real product
      "deliverable_cities": [str],      # only when item_deliverable=false (capped at 60)
      "perishable_warning": str | null  # populated when product_id is perishable
    }
ParametersJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already mark it read-only/non-destructive, but the description adds substantial behavior the annotations cannot carry: fee depends on cart+currency, LKR fees are capped at 25% of item value (min LKR 300, 50% for remote cities) while USD is fixed, an unknown product_id is silently ignored, and the `reason` text must not be interpreted. This is exactly the kind of non-obvious trait an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core answer, but the block is long and the Args section duplicates the input schema's own descriptions nearly verbatim, plus it repeats the full output schema already declared in the tool definition. Some sentences (same-day rule, perishable warning) earn their place; others are redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with an output schema and rich annotations, the description covers everything an agent needs: fee-basis semantics ('cart'/'max'/'fixed'), the product_id/item_deliverable interaction, date fallback via next_available_date, and the warning that a no-product_id check may differ from one with it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema itself is richly described, and the prose Args section largely restates it, so marginal value is limited. It does add genuine semantics beyond the schema, e.g. that `cart` must match the lines sent to create_order and that omitting it yields an 'up to' rather than exact fee.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource+scope: checks delivery feasibility of a city on a date and returns the delivery fee. It is clearly distinguishable from siblings, and explicitly frames itself as the pre-flight check that predicts what kapruka_create_order will charge.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use rules (pass `cart` for the exact fee, pass `product_id` whenever a product is named, check `item_deliverable` before relying on it) and a when-not-to: do not attempt kapruka_create_order with the same city when `item_deliverable` is false. Alternatives are named (deliverable_cities, island-wide alternative).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

kapruka_create_orderA
Idempotent
Inspect

Create a guest-checkout order on Kapruka and return a click-to-pay link.

Builds a Kapruka order from the supplied cart + recipient + delivery + sender,
then returns a checkout URL the customer opens in a browser to complete payment.
No Kapruka account is required. Prices are locked for the lifetime of the link
(60 minutes) — the customer pays exactly the quoted grand total even if the
catalog price changes meanwhile.

Free public tier limits: 30 orders per hour per client IP. Cart up to 30 items,
quantity up to 99 per item. A fresh idempotency key is generated per call so
retries on transient errors return the same checkout URL rather than duplicates.

Args:
    params (CreateOrderInput):
        - cart (list[CartItem]): 1–30 lines. Catalogue line: product_id, quantity (default 1), optional icing_text (cakes only).
          Custom cake line: custom_cake_request_id + phone — orders the cake Kapruka staff quoted via
          kapruka_custom_cake_status (status must be 'quoted'; quantity is always 1; never send a price).
          Lines can be mixed in one order — one delivery fee covers everything; the whole cart must be
          deliverable to delivery.city. Only place a custom cake order after the customer clearly
          accepted the quoted total.
        - recipient (Recipient): name + phone (E.164 +9477… or local 077…)
        - delivery (Delivery): address, city (must be Kapruka-deliverable — use kapruka_list_delivery_cities), location_type (house/apartment/office/other, default house), date (YYYY-MM-DD, today-or-future Asia/Colombo), optional instructions
        - sender (Sender): name + anonymous flag
        - gift_message (Optional[str]): Up to 300 chars
        - currency (str): LKR (default), USD, GBP, AUD, EUR
        - response_format (str): 'markdown' (default) or 'json'

Returns:
    str: Order confirmation with checkout URL.

    JSON schema:
    {
      "checkout_url": str,           # Open in browser to pay (no login required)
      "order_ref": str,              # e.g. "ORD-20260520-7823"
      "order_id": str,               # id used by the bank-deposit flow
      "summary": {
        "items_total":   number,
        "delivery_fee":  number,
        "addons_total":  number,
        "grand_total":   number,     # items_total + delivery_fee + addons_total
        "currency":      str
      },
      "expires_at": str              # ISO 8601 — link stops working after this
    }

    Error: "Error (<code>): <message>" on failure. Common codes:
      empty_cart, missing_field, past_delivery_date, product_not_found,
      product_out_of_stock, city_not_deliverable (city not in the network at
      all), date_not_deliverable, city_not_deliverable_for_item.

    Custom cake lines add: request_not_found (404 — wrong id/phone or staff
    removed it), quote_not_ready (409 — staff haven't priced it; check
    kapruka_custom_cake_status later), quote_expired (410 — submit a new
    kapruka_custom_cake_request). summary.items_total may differ from the
    quoted cake total by a few rupees (USD round-trip) — quote the summary
    numbers when asking for payment.

    city_not_deliverable_for_item (HTTP 422): at least one cart item (food /
    hotel cake / liquor) cannot reach delivery.city. NOTHING is created — the
    API never places a partial order and neither should you. The error text
    names every blocking item and lists the cities the whole cart CAN go to.
    Tell the customer which item blocks the order and offer to (a) change the
    city to one of those, or (b) remove/replace that item. Never retry with
    the same city. Avoid this entirely by calling kapruka_check_delivery with
    `product_id` for each limited item before ordering.
ParametersJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A5/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare readOnlyHint=false (write operation), idempotentHint=true, and destructiveHint=false. The description goes far beyond these: it discloses price locking for 60 minutes, free-tier rate limits, idempotency key behavior, and the crucial non-partial-order guarantee on city_not_deliverable_for_item. It also notes potential currency round-trip differences in summary.items_total for custom cakes. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with an opening summary, followed by Args and Returns sections, and bullet points for error codes. It is front-loaded with the core purpose and all additional sentences earn their place by covering behavioral, constraint, or routing details. No fluff or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is complete given the output schema exists and the schema already documents parameter shapes. It explains the return values (checkout URL, order ref, summary), error codes and their meanings, and the special handling for city_not_deliverable_for_item. An agent has everything needed to call the tool correctly, including when to call companion tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Even though schema description coverage is reported as 0%, the tool description adds substantial meaning beyond the schema: it explains the cart line structure (catalogue vs custom cake), phone format requirements, delivery city constraints, gift message length, supported currencies, and response_format options. The schema itself also has detailed descriptions, but the tool description reinforces and adds practical guidance (e.g., never send a price for custom cakes).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates a guest-checkout order and returns a click-to-pay link. It specifies the verb ('create'), the resource ('Kapruka order'), and the outcome, and distinguishes itself from siblings by naming the helper tools it coordinates with (kapruka_custom_cake_status, kapruka_list_delivery_cities, kapruka_check_delivery).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly explains when to use the tool (to place a guest checkout order) and provides critical exclusions: never retry with the same city after city_not_deliverable_for_item, and only place custom cake orders after the customer accepted the quoted total. It also references alternative tools for pre-checks, giving clear routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

kapruka_get_productA
Read-onlyIdempotent
Inspect

Fetch full details for a single Kapruka product by its product ID.

Returns name, description, price (with optional currency conversion), stock status,
images, variants, shipping info, delivery scope, and a direct product URL.

Discounts: `price` is what checkout charges, with any website discount already
applied; `compare_at_price` is the pre-discount price when one applies (null
otherwise). Each variant carries its own pair. Quote `price`.

Delivery scope: most gifts ship island-wide, but restaurant food, hotel cakes
and liquor only reach a limited city set (typically the Colombo area). The
`delivery` object is the authority — search results do NOT carry it. When
`delivery.island_wide` is false, tell the customer up front that the item is
delivered only to selected cities, and confirm their city with
kapruka_check_delivery(city, product_id) before promising anything. If
`deliverable_city_count` exceeds the returned list, the list is truncated —
say "and more", don't treat it as complete.

Note: Some IDs starting with 'CATSYM' are category landing pages, not purchasable
products — this tool will flag those clearly.

Args:
    params (GetProductInput):
        - product_id (str): Kapruka product ID (e.g. 'cakeXX000000')
        - currency (str): Price currency — LKR (default), USD, GBP, AUD, EUR
        - type (Optional[str]): Optional type hint (e.g. 'specialgifts')
        - response_format (str): 'markdown' (default) or 'json'

Returns:
    str: Product details in the requested format.

    JSON schema:
    {
      "id": str,
      "name": str,
      "description": str,
      "summary": str,
      "price": {"amount": float, "currency": str},
      "compare_at_price": {"amount": float, "currency": str} | null,
      "in_stock": bool,
      "stock_level": str,           # "low" | "medium" | "high"
      "category": {"id": str, "name": str, "slug": str, "path": str},
      "variants": [{"id": str, "name": str, "sku": str, "price": {...},
                    "in_stock": bool, "stock_level": str, "attributes": {...}}],
      "images": [str],              # list of full-resolution image URLs
      "attributes": {"type": str, "subtype": str, "weight": str, "vendor": str},
      "shipping": {"ships_from": str, "ships_internationally": bool, "restricted_countries": [str]},
      "delivery": {
        "island_wide": bool,
        "deliverable_city_count": int,   # only when island_wide=false; TRUE total
        "deliverable_cities": [str]      # only when island_wide=false; capped at 60
      },
      "rating": null,
      "url": str
    }

    Error: "Error: <message>" on failure.
ParametersJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A4.4/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial behavioral context beyond them: discount semantics for price vs compare_at_price, the limited-city delivery constraint, the deliverable_cities truncation-at-60 caveat, and the CATSYM non-purchasable flag. This is real operational guidance, not repetition.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the one-line purpose, then organized into price, delivery, and note sections with clear headers. Some delivery prose is longer than strictly needed, but each block carries actionable instructions and nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A full response schema is documented, so return values need no prose, and the description still covers edge cases an agent needs: discount interpretation, truncated city lists, category landing pages, and the 'Error: <message>' failure format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The Args section enumerates product_id examples and lists currency options (LKR default, USD/GBP/AUD/EUR) and response_format values, largely mirroring the input schema. The only added nuance is that 'type' is rarely needed. Adequate but adds little beyond the schema fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Fetch full details for a single Kapruka product') scoped by 'by its product ID', which distinguishes it from kapruka_search_products by implying an already-known ID. An agent can identify the tool without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear conditional guidance: when to call kapruka_check_delivery(city, product_id) before promising delivery, and how to treat CATSYM IDs that are landing pages rather than products. It does not explicitly say to find IDs via kapruka_search_products first, but the workflow context is strong.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

kapruka_list_categoriesA
Read-onlyIdempotent
Inspect

List top-level Kapruka product categories by name with browse URLs.

Returns the site's NAVIGATION categories plus the public Kapruka.com URL for each
category landing page — useful for sending a customer to a category to browse.

These names are NOT search filters. kapruka_search_products filters on search
facets, a different vocabulary (e.g. navigation 'Electronic' vs facet 'Electronics',
'Cakes' vs 'Kapruka Cakes'); every search response lists its valid facet names
under facets.categories. Use those for `category`, never these. Internal IDs and
product counts are not exposed. Results are cached for 30 minutes server-side.

Args:
    params (ListCategoriesInput):
        - depth (int): Sub-category levels to include, 1 or 2 (default 1)
        - response_format (str): 'markdown' (default) or 'json'

Returns:
    str: Category tree in the requested format.

    JSON schema:
    {
      "categories": [
        {
          "name": str,
          "url": str,                  # kapruka.com category landing page
          "children": [{"name": str, "url": str, "children": [...]}]
        }
      ]
    }

    Error: "Error: <message>" on failure.
ParametersJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A4.5/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Despite readOnlyHint and idempotentHint annotations, the description adds valuable context: cache duration (30 minutes), that internal IDs and product counts are not exposed, and the exact error format. It also clarifies the data source (navigation vs facets).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is somewhat verbose but well-structured: opening summary, usage guidance, parameter details, and return schema. It is front-loaded with the purpose and includes critical warnings. Minor redundancy in the JSON schema block, but overall earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only listing tool with an output schema and strong annotations, the description is comprehensive. It covers what to do, what not to do, caching, error handling, and parameter details. Nothing essential is missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema description coverage at 0%, the description carries the burden. It explains depth levels (1 or 2) and response_format options (markdown/json), directly paralleling the schema fields, which compensates. Could add more but is effective.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists top-level product categories with names and URLs, a specific and distinct purpose. However, it doesn't explicitly contrast with siblings beyond the search distinction, so it's not a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly warns against using these names as search filters and directs the user to use facets.categories from search responses, naming the sibling kapruka_search_products. This is a clear 'when not to use' with alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

kapruka_list_delivery_citiesA
Read-onlyIdempotent
Inspect

List or search Sri Lankan cities Kapruka delivers to.

Use the `query` param to filter (e.g. "colombo" → all Colombo zones,
"anur" → Anuradhapura). Without a query you get the first 25 cities
alphabetically, which is rarely what an agent needs — pass a query.

Returns canonical city names (use these as the `city` argument to
kapruka_check_delivery) plus any common aliases / vernacular spellings.

Args:
    params (ListDeliveryCitiesInput):
        - query (Optional[str]): Partial match filter
        - limit (int): Max results, 1–50 (default 25)
        - response_format (str): 'markdown' (default) or 'json'

Returns:
    str: Cities list in the requested format.

    JSON schema:
    {
      "cities": [{"name": str, "aliases": [str]}],
      "total_matched": int,
      "showing": int
    }
ParametersJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds substantial behavioral detail beyond annotations: default shows first 25 cities alphabetically, query enables partial case-insensitive match, response_format can be markdown or json, and returns canonical names plus aliases. The caveat about the default being rarely needed is honest and useful.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured and front-loaded: opening purpose, usage guidance, Args section, and Returns with JSON schema. Each sentence contributes relevant information without unnecessary verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's list/search functionality and available output schema, the description covers default behavior, filtering, response formats, and return structure. It even includes a JSON schema excerpt, making it complete for an agent to call correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description restates parameter names and types, but also adds illustrative examples and meaning beyond the schema. It explains the query behavior with concrete examples and clarifies that returned names should be used as the `city` argument, enriching parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it lists or searches Sri Lankan cities Kapruka delivers to, with a specific verb (list/search) and resource (cities). It distinguishes from sibling kapruka_check_delivery by noting it returns canonical city names to use as the `city` argument for that tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit usage guidance: warns that without a query the default alphabetical limit is rarely what an agent needs, and gives example filters ('colombo' → Colombo zones, 'anur' → Anuradhapura). It implies the relationship to kapruka_check_delivery but does not state when to avoid using this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

kapruka_render_options_cardA
Read-onlyIdempotent
Inspect

Render 1-4 products as ONE shareable JPEG "menu" card and return its URL.

The card shows each product's photo with a big numbered badge (the ref you
assign), and its name + price printed under the photo. Built for chat
commerce (WhatsApp): send the image, tell the customer "reply 1, 2 or 3",
and they pick without opening links. No AI is involved — the image is
server-composited from the live catalog data, so prices match what the
product tools return.

Ref numbering contract: refs are yours to assign — use sequential numbers
per conversation and NEVER reuse one (if the first card was 1-3, the next
card starts at 4). A number must keep meaning the same product for the whole
conversation.

Args:
    params (RenderOptionsCardInput):
        - items (list[CardProduct]): 1-4 of {product_id, ref}
        - currency (str): LKR (default), USD, GBP, AUD, EUR
        - courtesy ({currency, per_usd}, optional): home-currency figure printed
          under each USD price ("≈ JPY 2,544"); the caller's rate, echoed back
        - footer_note (str, optional): appended to the footer reply hint

Returns:
    str: JSON:
    {
      "card_url": str,              # public JPEG URL — send this as the image
      "items": [{"ref": int, "product_id": str, "name": str,
                  "price": {"amount": float, "currency": str},
                  "price_note": str | null, "url": str}],
      "courtesy": {"currency": str, "per_usd": float} | null,  # what was printed, or null
      "unavailable": [str]          # product_ids that failed to load (omitted from card)
    }

    Error: "Error: <message>" when no product could be loaded.
ParametersJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations (readOnlyHint, openWorldHint, idempotentHint, destructiveHint), the description discloses meaningful behavior: server-side composition with no AI, live catalog pricing, the unavailable-products failure behavior, the 'Error: ...' return mode, and the critical ref-numbering never-reuse contract. These are details an agent could not infer from annotations or the schema alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured: a one-line summary, a short use-case paragraph, the ref numbering contract, an Args breakdown, and a return contract. It is longer than average, but each section earns its place and the layout makes it highly scannable for an agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers invocation constraints (1-4 items, sequential refs, currency behavior, courtesy rules), return shape (card_url, items, courtesy, unavailable), and error handling when no product loads. With the output schema also present, nothing essential is left for the agent to guess.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema description coverage is reported at 0%, the description's Args block fully compensates: items as 1-4 of {product_id, ref}, currency options with LKR default, courtesy as the caller's rate echoed back under USD prices, and footer_note appended to the reply hint. It also explains the ref numbering contract, which is essential semantic guidance beyond the raw field names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a precise verb and resource: 'Render 1-4 products as ONE shareable JPEG menu card and return its URL.' It further narrows the purpose with the WhatsApp chat-commerce scenario, numbered ref badges, and the explicit statement that no AI is involved, distinguishing it from the product/search/order siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly explains when to use the tool: in chat commerce where the customer replies with a number, and notes that the image is server-composited from live catalog data so prices match what the product tools return. It does not explicitly name an alternative tool or a when-not-to-use condition, but the intended usage context is strongly implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

kapruka_search_productsA
Read-onlyIdempotent
Inspect

Search for products on Kapruka.com by keyword, with optional category filter and pagination.

Returns a ranked list of matching products with prices, stock status, images, and URLs,
plus the category facets available for the query (facets.categories) — the names that
work in `category` to narrow the same search.
Supports cursor-based pagination — pass next_cursor from one response into the next call.
Pagination is capped at 3 pages per query to discourage catalog enumeration; for broader
discovery, refine the query or narrow with a facet instead.

Queries must be at least 3 characters and contain specific terms — pure stopword queries
(e.g. "the", "a an") are rejected.

Relevance: the API matches ANY single query word, so extra words add loosely related
results rather than narrowing. Search the thing the customer wants (the head noun) and
check the product names actually contain it before presenting them.

Prices and min_price/max_price are both in `currency` — pass the customer's own budget
in their own currency; do not convert it. A row's `price` is the discounted price
checkout charges (the bounds filter on it); `compare_at_price` is set when on sale.

Search results carry NO delivery-scope information. Food, hotel cakes and liquor
are delivered only to selected cities — never infer deliverability from a search
hit. Before quoting delivery on a specific item, call kapruka_get_product (read
`delivery.island_wide`) or kapruka_check_delivery with `product_id`.

Args:
    params (SearchProductsInput):
        - q (str): Search query (e.g. 'birthday cake', 'roses', 'tea gift'). Min 3 chars.
        - category (Optional[str]): A facet name from a previous search's facets.categories
        - limit (int): Results per page, 1–50 (default 10)
        - cursor (Optional[str]): Pagination cursor from previous response
        - currency (str): LKR (default), USD, GBP, AUD, EUR
        - min_price (Optional[float]): Min price (inclusive) in `currency`
        - max_price (Optional[float]): Max price (inclusive) in `currency`
        - in_stock_only (bool): Restrict to in-stock items (default false)
        - sort (str): 'relevance' | 'price_asc' | 'price_desc' | 'newest' | 'bestseller'
        - include_stubs (bool): Deprecated, no effect
        - response_format (str): 'markdown' (default) or 'json'

Returns:
    str: Search results in the requested format.

    JSON schema:
    {
      "results": [
        {
          "id": str,
          "type": "product",
          "name": str,
          "summary": str,
          "price": {"amount": float | null, "currency": str},
          "compare_at_price": {"amount": float, "currency": str} | null,
          "in_stock": bool,
          "stock_level": str,
          "image_url": str | null,
          "category": {"id": str, "name": str, "slug": str},
          "rating": null,
          "ships_internationally": bool,
          "url": str
        }
      ],
      "next_cursor": str | null,     # null after page 3 even if upstream has more
      "total_estimate": int,         # index hits for the query words (any-word match)
      "applied_filters": {"q": str, "category": str, "currency": str, ...},
      "facets": {"categories": [{"name": str, "count": int}]},
      "category_filter_dropped": str,   # only when `category` was not a facet here
      "valid_categories": [str]         # ...and the facet names that are
    }

    Error: "Error: <message>" or "No products found for '<query>'" on failure.
ParametersJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond annotations (which only say readOnly/idempotent/openWorld): discloses the 3-page pagination cap, stopword rejection, ANY-word matching semantics, that search carries NO delivery-scope info, price/compare_at_price semantics, and the category facet drop behavior. This is rich, non-obvious behavioral context an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded purpose sentence, then clearly sectioned behavioral guidance (returns, pagination, queries, relevance, currency, delivery). Slightly long with some repetition between prose and Args section, but every paragraph earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a search tool with an output schema present, the description covers the crucial non-obvious traps: the 3-page cap, facet-vs-department vocabulary, ANY-word relevance, currency non-conversion, and the delivery-scope caveat with explicit sibling routing. An agent has everything needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is reported at 0%, so the description must compensate; it explains q (min 3 chars, specific terms), category (facet names only, listing 'Kapruka Cakes' etc.), cursor (from next_cursor), currency, and min/max_price (inclusive, in currency). It does not spell out sort enum values or limit/in_stock_only defaults, but the schema does cover those.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search for products on Kapruka.com') plus scope (keyword, optional category filter, pagination). Clearly distinguishable from siblings like kapruka_get_product (single item lookup) and kapruka_list_categories (navigation taxonomy).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: for delivery-scope on a specific item, use kapruka_get_product or kapruka_check_delivery with product_id; to narrow, use facets from a prior search. Names the alternatives and the conditions that select them.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

kapruka_track_orderA
Read-only
Inspect

Look up status and delivery progress for a Kapruka order by order number.

Returns current status (received / confirmed / out-for-delivery / delivered /
cancelled), the recipient and delivery details on file, a timestamped progress
timeline, the cart contents, and flags for whether a delivery photo or video is
available. Use this after a customer has placed and paid for an order and reads
back the order number from their confirmation email or the order complete page.

The order number is NOT the `order_ref` returned by kapruka_create_order
(which is the pre-payment checkout reference). Once the customer completes
payment in the browser, Kapruka emails them a separate order number — that
is what this tool expects.

Args:
    params (TrackOrderInput):
        - order_number (str): Kapruka order number (e.g. 'VIMP34456CB2')
        - response_format (str): 'markdown' (default) or 'json'

Returns:
    str: Order tracking details in the requested format.

    JSON schema:
    {
      "order_number": str,
      "pnref": str,                 # internal payment reference (numeric; not the same as order_number)
      "status": str,                # received | confirmed | shipped | delivered | cancelled | ...
      "status_display": str,        # human label
      "order_date": str,            # human-formatted, Asia/Colombo
      "delivery_date": str,         # human-formatted
      "shipped_date": str | null,
      "amount": str,                # LKR string (e.g. "15500.00")
      "payment_method": str,
      "comments": str | null,
      "recipient": {"name": str, "phone": str, "address": str, "city": str},
      "greeting_message": str | null,
      "special_instructions": str | null,
      "progress": [{"step": str, "timestamp": str}],
      "live_tracking_available": bool,
      "has_delivery_video": bool,
      "has_delivery_photo": bool,
      "items": [{"product_id": str, "name": str, "quantity": int, "selling_price": float}]
    }

    Error: "Error: <message>" on failure (e.g. order not found).
ParametersJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description goes far beyond the annotations by detailing the exact statuses returned, the contents of the progress timeline, availability of delivery photo/video flags, and the error message format. Even though readOnlyHint and destructiveHint are already provided, the description adds meaningful behavioral context (e.g., live_tracking_available boolean, payment reference field) that helps an agent anticipate results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-organized: it starts with the core purpose, provides usage context, lists parameters, and includes a return schema. Every sentence contributes value, and the structure makes it easy to scan. The embedded JSON schema is verbose but justified given the complex return payload.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (multiple statuses, nested recipient/items objects, error handling), the description is comprehensive. It explains when to use it, what input to provide, what output to expect, and includes the caveat about order_ref. The annotations and detailed schema round out the context, making the tool fully actionable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description's Args section essentially mirrors the input schema, which already contains detailed descriptions for both parameters, including the crucial order_ref distinction. Thus, the description adds little new semantic meaning beyond what the schema provides. The example format ('VIMP34456CB2') is helpful but not a significant increment.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Look up') and resource ('status and delivery progress for a Kapruka order by order number'), clearly distinguishing it from sibling tools like kapruka_create_order. It also outlines the exact output, making the purpose unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states when to use the tool ('after a customer has placed and paid for an order and reads back the order number from their confirmation email or the order complete page') and warns against using the order_ref from kapruka_create_order. This provides clear when-to-use and when-not-to-use guidance, effectively differentiating it from related tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedkapruka_check_delivery4 fields changed
      • addedInput schema / $defs / CheckDeliveryInput / properties / cart
        Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "$ref": "#/$defs/DeliveryCartLine"
+      },
+      "maxItems": 30,
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "The items the customer is buying (product_id, quantity, optional icing_text) — the same lines you will send to kapruka_create_order. With it the answer gives the EXACT delivery fee checkout will charge; without it, only the most it can be.",
+  "title": "Cart"
+}
      • addedInput schema / $defs / CheckDeliveryInput / properties / currency
        Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "The currency the customer will check out in (LKR or USD; GBP/AUD/EUR check out in USD). Decides which delivery fee applies: Sri Lankan customers pay a fee capped by the cart value, overseas customers a fixed USD fee. Default LKR.",
+  "title": "Currency"
+}
      • addedInput schema / $defs / CheckDeliveryInput / properties / other_items_total
        Added value: +{
+  "anyOf": [
+    {
+      "minimum": 0,
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "LKR value of items not listed in `cart` (e.g. a quoted custom cake's total). Added to the cart value for the fee.",
+  "title": "Other Items Total"
+}
      • addedInput schema / $defs / DeliveryCartLine
        Added value: +{
+  "description": "A catalogue cart line, the same shape kapruka_create_order takes.\n\nCustom cake lines cannot be priced here; pass the quote's total as\n`other_items_total` instead.",
+  "properties": {
+    "icing_text": {
+      "anyOf": [
+        {
+          "maxLength": 120,
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Set when the cake carries icing text — the checkout adds a small charge for it.",
+      "title": "Icing Text"
+    },
+    "product_id": {
+      "maxLength": 50,
+      "minLength": 3,
+      "pattern": "^[A-Za-z0-9_\\-]+$",
+      "title": "Product Id",
+      "type": "string"
+    },
+    "quantity": {
+      "default": 1,
+      "maximum": 99,
+      "minimum": 1,
+      "title": "Quantity",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "product_id"
+  ],
+  "title": "DeliveryCartLine",
+  "type": "object"
+}
  2. 1 tool update
    • Changedkapruka_search_products2 fields changed
      • changedInput schema / $defs / SearchProductsInput / properties / category / description
        Previous value: -"Filter by SUBCATEGORY FACET NAME — the same value the website's search uses in its `subcat=` parameter and shows in its left sidebar, e.g. 'Kapruka Cakes', 'Fresh Flowers', 'Birthday', 'Greeting Cards', 'Cake And Flower', 'Home And Lifestyle', 'Grocery Items'. These are narrower than a department and the valid set DEPENDS ON THE QUERY. Department words ('Cakes', 'Flowers', 'Toys') and most values from kapruka_list_categories are NOT valid here and return nothing. When the filter matches nothing this tool retries without it and says so, so a wrong value costs relevance, not results. If unsure, leave it unset and put the words in `q`."New value: +"Filter by a SEARCH FACET name. Every search response lists the valid ones for its words under facets.categories (e.g. 'Kapruka Cakes', 'Fresh Flowers', 'Electronics', 'Mobile Phones', 'Greeting Cards') — search once without a category, then narrow with one of those names. Department words ('Cakes', 'Flowers') and names from kapruka_list_categories (the site's navigation, a different vocabulary) are NOT facet names. Case and spacing don't matter. A name that isn't a facet for this query is dropped: you get results without it plus the list of valid names."
      • changedInput schema / $defs / SearchProductsInput / properties / include_stubs / description
        Previous value: -"If false (default), category landing pages (CATSYM entries, price=0) are filtered out."New value: +"Deprecated, has no effect. Kept so existing callers don't break: since 2026-09-26 the API never returns category landing pages from a search."
  3. 4 tool updates
    • Changedkapruka_create_order1 field changed
      • changedInput schema / $defs / CreateOrderInput / properties / currency / description
        Previous value: -"Pricing currency. Supported: LKR, USD, GBP, AUD, CAD, EUR."New value: +"Pricing currency. Supported: LKR, USD, GBP, AUD, EUR."
    • Changedkapruka_get_product1 field changed
      • changedInput schema / $defs / GetProductInput / properties / currency / description
        Previous value: -"Price currency. Supported: LKR, USD, GBP, AUD, CAD, EUR"New value: +"Price currency. Supported: LKR, USD, GBP, AUD, EUR"
    • Changedkapruka_render_options_card1 field changed
      • changedInput schema / $defs / RenderOptionsCardInput / properties / currency / description
        Previous value: -"Price currency: LKR, USD, GBP, AUD, CAD, EUR."New value: +"Price currency: LKR, USD, GBP, AUD, EUR."
    • Changedkapruka_search_products1 field changed
      • changedInput schema / $defs / SearchProductsInput / properties / currency / description
        Previous value: -"Price currency. Supported: LKR, USD, GBP, AUD, CAD, EUR"New value: +"Price currency. Supported: LKR, USD, GBP, AUD, EUR"
  4. 1 tool update
    • Changedkapruka_search_products1 field changed
      • changedInput schema / $defs / SearchProductsInput / properties / category / description
        Previous value: -"Filter by category name (e.g. 'Birthday', 'Cakes', 'Flowers'). Case-insensitive."New value: +"Filter by SUBCATEGORY FACET NAME — the same value the website's search uses in its `subcat=` parameter and shows in its left sidebar, e.g. 'Kapruka Cakes', 'Fresh Flowers', 'Birthday', 'Greeting Cards', 'Cake And Flower', 'Home And Lifestyle', 'Grocery Items'. These are narrower than a department and the valid set DEPENDS ON THE QUERY. Department words ('Cakes', 'Flowers', 'Toys') and most values from kapruka_list_categories are NOT valid here and return nothing. When the filter matches nothing this tool retries without it and says so, so a wrong value costs relevance, not results. If unsure, leave it unset and put the words in `q`."
  5. 1 tool update
    • Changedkapruka_render_options_card3 fields changed
      • addedInput schema / $defs / Courtesy
        Added value: +{
+  "additionalProperties": false,
+  "description": "A home-currency approximation to print under each USD price.\n\nThe CALLER supplies the rate it used for its own chat text, so the card and\nthe text agree to the unit; the card never converts on its own. Only\napplied when the card is priced in USD — the courtesy figure describes\nwhat a USD charge will look like on the customer's statement.",
+  "properties": {
+    "currency": {
+      "description": "ISO-4217 code of the customer's home currency, e.g. JPY.",
+      "maxLength": 3,
+      "minLength": 3,
+      "pattern": "^[A-Za-z]{3}$",
+      "title": "Currency",
+      "type": "string"
+    },
+    "per_usd": {
+      "description": "Units of that currency per 1 USD, as used for the chat text.",
+      "exclusiveMaximum": 1000000,
+      "exclusiveMinimum": 0,
+      "title": "Per Usd",
+      "type": "number"
+    }
+  },
+  "required": [
+    "currency",
+    "per_usd"
+  ],
+  "title": "Courtesy",
+  "type": "object"
+}
      • addedInput schema / $defs / RenderOptionsCardInput / properties / courtesy
        Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/Courtesy"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional: print '≈ <home currency>' under each USD price (see Courtesy). Ignored unless currency is USD."
+}
      • addedInput schema / $defs / RenderOptionsCardInput / properties / footer_note
        Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 60,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional short note appended to the footer's reply hint, e.g. 'Checkout charges USD'.",
+  "title": "Footer Note"
+}
  6. 1 tool update
    • Changedkapruka_create_order17 fields changed
      • addedInput schema / $defs / CartItem / description
        Added value: +"One cart line — EITHER a catalogue product OR a quoted custom cake.\n\nCatalogue line:   {\"product_id\": \"...\", \"quantity\": 1, \"icing_text\": \"...\"}\nCustom cake line: {\"custom_cake_request_id\": \"...\", \"phone\": \"+9477...\"}\nThe custom cake line is turned into the staff-quoted cake server-side\n(name, picture, price); quantity is always 1 and no price is ever sent."
      • addedInput schema / $defs / CartItem / properties / custom_cake_request_id
        Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 80,
+      "minLength": 6,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "request_id of a custom cake that kapruka_custom_cake_status reports as 'quoted'. Orders the staff-quoted cake (quantity 1). Requires `phone`.",
+  "title": "Custom Cake Request Id"
+}
      • changedInput schema / $defs / CartItem / properties / icing_text / description
        Previous value: -"Cake icing text. Silently ignored for non-cake products."New value: +"Cake icing text. Silently ignored for non-cake products. Catalogue lines only."
      • addedInput schema / $defs / CartItem / properties / phone
        Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 30,
+      "minLength": 7,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "The customer.phone the custom cake request was made with (custom cake lines only).",
+  "title": "Phone"
+}
      • addedInput schema / $defs / CartItem / properties / product_id / anyOf
        Added value: +[
+  {
+    "maxLength": 80,
+    "minLength": 3,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
      • addedInput schema / $defs / CartItem / properties / product_id / default
        Added value: +null
      • changedInput schema / $defs / CartItem / properties / product_id / description
        Previous value: -"Kapruka product ID (e.g. 'cakeXX000000')."New value: +"Kapruka product ID (e.g. 'cakeXX000000'). Catalogue line."
      • removedInput schema / $defs / CartItem / properties / product_id / maxLength
        Removed value: -80
      • removedInput schema / $defs / CartItem / properties / product_id / minLength
        Removed value: -3
      • removedInput schema / $defs / CartItem / properties / product_id / type
        Removed value: -"string"
      • addedInput schema / $defs / CartItem / properties / quantity / anyOf
        Added value: +[
+  {
+    "maximum": 99,
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
      • changedInput schema / $defs / CartItem / properties / quantity / default
        Previous value: -1New value: +null
      • changedInput schema / $defs / CartItem / properties / quantity / description
        Previous value: -"Quantity (1–99)."New value: +"Quantity (1–99, default 1). Catalogue lines only."
      • removedInput schema / $defs / CartItem / properties / quantity / maximum
        Removed value: -99
      • removedInput schema / $defs / CartItem / properties / quantity / minimum
        Removed value: -1
      • removedInput schema / $defs / CartItem / properties / quantity / type
        Removed value: -"integer"
      • removedInput schema / $defs / CartItem / required
        Removed value: -[
-  "product_id"
-]
  7. 2 tool updates
    • Changedkapruka_check_delivery2 fields changed
      • changedInput schema / $defs / CheckDeliveryInput / properties / product_id / anyOf
        Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 80,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
      • changedInput schema / $defs / CheckDeliveryInput / properties / product_id / description
        Previous value: -"Optional product ID. If provided and the product looks perishable (cake/flower/combo codes), a freshness warning is added when the chosen date is more than 1 day out."New value: +"Product ID to check the city AGAINST THAT ITEM'S delivery scope. Food, hotel cakes and liquor only reach selected cities — always pass this when a customer names a product and a city, and only promise delivery if `available` is true. Also adds a freshness warning for perishable codes (cake/flower/combo) when the date is >1 day out."
    • Changedkapruka_create_order1 field changed
      • changedInput schema / $defs / Delivery / properties / city / description
        Previous value: -"Must be a Kapruka delivery city — use kapruka_list_delivery_cities to look up valid names."New value: +"Must be a Kapruka delivery city (canonical name from kapruka_list_delivery_cities) that EVERY cart item can reach. The order ships as one shipment, so food / hotel cake / liquor items restrict the whole cart to their city set — verify with kapruka_check_delivery(city, product_id) first; otherwise the order is rejected with city_not_deliverable_for_item."
  8. 2 tool updates
    • Changedkapruka_create_order1 field changed
      • changedInput schema / $defs / CartItem / properties / product_id / description
        Previous value: -"Kapruka product ID (e.g. 'cake00ka002034')."New value: +"Kapruka product ID (e.g. 'cakeXX000000')."
    • Changedkapruka_get_product1 field changed
      • changedInput schema / $defs / GetProductInput / properties / product_id / description
        Previous value: -"Kapruka product ID (e.g. 'cake00ka002034', 'EF_PC_CHOC0V2774P00065')"New value: +"Kapruka product ID (e.g. 'cakeXX000000', 'EF_PC_CHOC0V2774P00065')"
  9. 3 tool updates
    • Removedkapruka_customer_addresses
    • Removedkapruka_customer_details
    • Removedkapruka_order_history
  10. 3 tool updates
    • Addedkapruka_customer_addresses
    • Addedkapruka_customer_details
    • Addedkapruka_order_history
  11. 1 tool update
    • Addedkapruka_render_options_card
  12. 1 tool update
    • Addedkapruka_track_order
  13. 1 tool update
    • Addedkapruka_create_order
  14. 5 tool updates
    • First observedkapruka_check_delivery
    • First observedkapruka_get_product
    • First observedkapruka_list_categories
    • First observedkapruka_list_delivery_cities
    • First observedkapruka_search_products

Related MCP Connectors

Related MCP Servers

Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources