Skip to main content
Glama

Trueprice

Product Finder

find_products
Read-onlyIdempotent

Filter every product Trueprice tracks across its Shopify stores, like the Product Finder at /product-finder (same filters, same results as GET /api/v1/finder). Drops are % below the product's highest in-stock price in the last 7 or 30 days (daily history starts 2026-11-13). new_days = listed by the store within N days (first seen after Trueprice's first read of that store). One currency at a time (default USD). Sorts: drop (dropped products first, biggest drop first), new (new listings first), price (lowest first), rating (best rated first), reviews (most reviewed first), rank (each product type's cheapest in-stock products first). Each row has rating + reviews from the store's review app and type_rank (#rank cheapest of of in-stock products of its product_type and currency). 20 results a page; each has a url to its Trueprice price-history page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
sortNodrop
brandNoBrand (Shopify vendor), exact, any case
queryNoWords that must all be in the title
storeNoStore domain, e.g. example.com
drop_7dNoMinimum % drop over 7 days (1-100)
currencyNoISO currency, default USD
drop_30dNoMinimum % drop over 30 days (1-100)
has_codeNoOnly stores with a checked promo code
in_stockNo
new_daysNoOnly products newly listed in the last N days
max_priceNo
min_priceNo
min_ratingNoMinimum star rating from the store's review app
min_reviewsNoMinimum number of reviews
product_typeNoShopify product type, exact, any case

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, and the description adds real substance on top: how 'drop' is computed against the 7/30-day in-stock high, that daily history begins 2026-11-13, what new_days actually measures (first seen after Trueprice's first read), and page size of 20. It also describes row contents (rating, reviews, type_rank, url) and how each sort orders results.

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 core purpose, then filters, then sorts, then row shape and pagination — an efficient information order. The sort enumeration is long and reads as a run-on, but every clause carries operational meaning and nothing is filler.

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 16-parameter, no-output-schema tool this covers a lot: result row fields, page size, currency constraint and derived metric definitions. Remaining gaps are the page maximum of 50 and the unexplained price/in-stock/code filters, which the schema partially but not fully documents.

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 coverage is 69%, and the description compensates for much of the gap by defining drop_7d/drop_30d as minimum % drop, expanding every sort enum value with its ordering, and restating the single-currency default. It leaves min_price, max_price, in_stock and has_code unexplained, so it is strong rather than complete.

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?

States a specific verb and resource: it filters every product Trueprice tracks across Shopify stores, and anchors it to a concrete UI/API equivalent (/product-finder, GET /api/v1/finder). It does not name or distinguish against the sibling search_products, so an agent must infer the difference, keeping it below 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 Guidelines3/5

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

Usage is implied by the filter semantics (use drop_7d/drop_30d for price drops, new_days for new listings, etc.), and the one-currency-at-a-time constraint is stated. However, there is no explicit when-to-use-this-vs-search_products guidance and no exclusions, so an agent still has to guess the boundary between the two finders.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources