Skip to main content
Glama
Sign In

Lowcart delivered prices

by com.getlowcart
OverviewDiscussionsAdmin

Find the cheapest delivered price

find_delivered_price
Read-only

Finds the Shopify stores that deliver a product to a country and ranks them by the final total a shopper pays: item price, shipping to that country, the best confirmed code, sales tax or VAT, and import fees. Each total is read from the store's own checkout for that country (no order is placed), and every offer says where import duties are paid: none (ships locally), included in the price, paid at checkout, billed at the door (estimate added), may be billed at the door (not included), or unknown origin. Final totals rank first. Works for any product sold by Shopify stores: electronics, kitchen appliances, drinkware, shoes, clothing, fitness gear, toys, home goods, supplements, beauty and more. Amazon, Daraz, Sephora and other marketplace links are read for the product name only. Amounts are in US dollars with the local currency alongside. Use for questions like "where is a Ninja CREAMi cheapest delivered to the US", "what will a Stanley Quencher 40 oz really cost delivered to Australia" or "cheapest UGG Tasman slippers delivered to the UK".

Input Schema

NameRequiredDescriptionDefault
stateNoUS only: two letter state code, for sales tax.
countryYesTwo letter delivery country code, for example US, GB, AU, DE.
productYesBrand plus product name, for example "Ninja CREAMi Deluxe", "Stanley Quencher 40 oz" or "Beauty of Joseon Relief Sun", or a product link (Shopify stores are read; Amazon and other marketplace links are read for the name only). A bare type ("toner", "headphones") or a brand alone ("COSRX") is refused with a message asking for both.
postal_codeNoOptional delivery ZIP or postcode, for shipping (and US and Canadian sales tax) to that exact area. Works for the US, Canada, the UK, Australia, the EU and most other supported countries.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / product / description
      Previous value: -"Brand plus product name, for example \"Beauty of Joseon Relief Sun\" or \"Stanley Quencher 40 oz\", or a product link (Shopify stores are read; Amazon and other marketplace links are read for the name only). A bare type (\"toner\", \"headphones\") or a brand alone (\"COSRX\") is refused with a message asking for both."New value: +"Brand plus product name, for example \"Ninja CREAMi Deluxe\", \"Stanley Quencher 40 oz\" or \"Beauty of Joseon Relief Sun\", or a product link (Shopify stores are read; Amazon and other marketplace links are read for the name only). A bare type (\"toner\", \"headphones\") or a brand alone (\"COSRX\") is refused with a message asking for both."
  2. Changed1 schema field changed
    • changedInput schema / properties / product / description
      Previous value: -"Brand plus product name, for example \"Beauty of Joseon Relief Sun\", or a store product link. Beauty and skincare only: a bare type (\"toner\") or a brand alone (\"COSRX\") is refused with a message asking for both."New value: +"Brand plus product name, for example \"Beauty of Joseon Relief Sun\" or \"Stanley Quencher 40 oz\", or a product link (Shopify stores are read; Amazon and other marketplace links are read for the name only). A bare type (\"toner\", \"headphones\") or a brand alone (\"COSRX\") is refused with a message asking for both."
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare read-only, non-destructive and open-world, and the description still adds substantial context: totals are read from the store's own checkout, no order is placed, and each offer is labelled with one of six import-duty payment states. This is behavior an agent cannot infer from the schema or annotations.

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 purpose and ranking logic are front-loaded in the first two sentences, which earns its place. The long product-category enumeration (electronics, drinkware, shoes, supplements, beauty...) is padding that could be trimmed without losing meaning.

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

Completeness4/5

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

For a read-only open-world search with no output schema, the description covers what is returned (ranked totals broken into item, shipping, code, tax, duties, plus currency) and the duty-payment semantics. It does not address result count, pagination, or behavior when no store carries the product, so it is not fully complete.

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 every parameter (state, country, product, postal_code) is already documented with format and purpose, which sets the baseline at 3. The description reinforces the product-refusal rule and currency handling but adds no syntax or format detail beyond the schema.

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 states a specific verb and resource (finds Shopify stores delivering a product to a country, ranked by delivered total) and enumerates exactly which cost components are summed. It is clearly distinguishable from the sibling import_fee_rules, which appears to supply the rule data this tool consumes.

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 concrete trigger questions ("where is a Ninja CREAMi cheapest delivered to the US") and a scope boundary (marketplace links are read for the product name only; bare types or brands are refused). It never names an alternative tool or states when not to use this one, so it stops short of the 5 bar.

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

All Lowcart delivered prices toolsInspect
Try in Browser
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources