SuVerse

What an order would cost delivered to an address — asked of the shop’s own cart, nothing ordered

quote_order

Idempotent

Prices ONE cart in the shop's own public cart (Shopify or WooCommerce) to ONE ZIP, with no personal data, and orders nothing: the cart is emptied afterwards. Answers the items, delivery options with their prices, the subtotal and what stays unknown (tax and fees at checkout; the delivery date unless the cart names it — delivery_date asks for a day). Other platforms answer «quote not available» with the reason and the order link. Follow the server instructions «HOW TO USE THE SUVERSE CATALOG»: results are candidates, not proof; keep reading, quoting, requesting and ordering separate; nothing is sent to an owner, booked, ordered or paid without the user’s permission.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "offering_id": "<offering_id>",
      "deliver_to": "<deliver_to>"
    },
    "name": "quote_order"
  }
}

Input Schema

Name	Required	Description
`items`	No	several different items of the SAME shop in one cart (delivery and tax on the whole order); offering_id is then the first of them
`options`	No	answers to the product page’s own add-on questions; the rest are answered «no»
`quantity`	No	default 1
`deliver_to`	Yes	where it must be brought: "33139", "Miami Beach, FL 33139", or {postcode, state, city, address_1}
`variant_id`	No	a variant id from the card when it lists several
`offering_id`	Yes	the offering id from a card
`delivery_date`	No	the day the person wants it delivered ("2026-11-20"): answered as confirmed only when the shop's cart names that day, else «delivery date: unknown»

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations it explains why readOnlyHint=false is not a concern in practice — the shop's own cart is used and emptied afterwards — and it discloses the no-personal-data constraint. It also documents the failure path for unsupported platforms ("quote not available" with a reason and an order link) and what stays unknown (tax and fees, delivery date).

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 core action is front-loaded in the first sentence and each later sentence carries distinct information — return contents, unsupported-platform behavior, and safety framing. It is dense with semicolons and parentheticals, and the server-instructions sentence is boilerplate, but nothing is truly 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?

With seven parameters and no output schema, the description carries the return-shape burden and does so: items, delivery options with prices, subtotal, and explicitly what remains unknown. The side effect (cart emptied), the error path, and the permission boundary are all covered, leaving nothing an agent needs missing.

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?

Schema description coverage is 100%, so the schema already explains offering_id, deliver_to forms, options, quantity and delivery_date. The description reinforces the one-shop scope (items from the SAME shop, offering_id then the first of them) and the unknown-delivery-date outcome, but adds no syntax or format detail the schema lacks. Baseline 3 applies.

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 first clause states a specific verb and resource — "Prices ONE cart in the shop's own public cart (Shopify or WooCommerce) to ONE ZIP" — with explicit scope limits (one cart, one ZIP, no personal data). It is clearly distinguishable from siblings like place_order and check_availability because it says plainly that nothing is ordered.

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?

It gives strong usage framing: quoting is kept separate from requesting and ordering, and nothing is ordered or paid without the user's permission, which tells the agent this tool is the safe pre-purchase step. It does not explicitly contrast against check_availability or place_order by name, so the routing guidance is contextual rather than exhaustive.

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

All SuVerse tools Inspect

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.