Skip to main content
Glama

Trueprice

Product price history

product_history
Read-onlyIdempotent

True price (true_price: lowest price it really sold at, from daily checks and archived snapshots), Stats per 30/90/180/365-day and all-time window (stats.windows: low/high with dates, average, price at window start, out-of-stock %, drop count, is_lowest, last_price_change), star rating and review count with history (rating), reviews from the store's review app (reviews: rating, count, star histogram, 3 recent reviews, Q&A, what reviewers mention), category rank among same-type products across stores (category_rank: #cheapest of N in stock, 30-day drop rank), units in stock per option (stock: qty, null = not limited, with its change history; variants[].stock), live price, every recorded price change, archived snapshots from before tracking began (archived, labelled "archived snapshot", not used in stats or score), 30/90-day and all-time low/average/high, deal score, best checked promo code and product spec (description, tags, options, SKUs, weights, images) for one product.

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": {
      "domain": "<domain>",
      "handle": "<handle>"
    },
    "name": "product_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesStore domain, e.g. example.com
handleYesShopify product handle
variantNoOptional option (variant) id from `variants[].id`: that size/colour's own price history

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description does add real context beyond that: archived snapshots are labelled "archived snapshot" and excluded from stats and score, and stock null means unlimited. However, it says nothing about cost/latency of fetching an all-time history, response shape, or any auth/scoping requirements, so the added value is moderate rather than rich.

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

Conciseness2/5

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

The entire description is one long run-on sentence built from nested parentheticals, which is hard to scan and not front-loaded — the key fact (one product, requires domain + handle) appears at the very end. Little is wasted in terms of false claims, but the structure actively impedes comprehension and many listed fields are near-duplicates (30/90/180/365-day windows plus 30/90-day and all-time low/average/high).

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?

There is no output schema, so the description must carry the return-value burden, and it does so exhaustively — covering true_price, stats windows, rating, reviews, category_rank, stock, live price, price changes, archived snapshots, deal score, promo codes and specs. What is missing is operational completeness: no guidance on choosing this over siblings and no sense of payload size or pagination. For a read-only single-product tool, the substantive gaps are limited.

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 all three parameters are already documented in the schema, including variant's "that size/colour's own price history". The description re-uses that same wording (`variants[].stock`, variant id) without adding syntax, defaults, or edge cases. Baseline 3 applies when the schema carries the parameter burden.

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

Purpose3/5

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

The description opens with a field dump ("True price (`true_price`...)") rather than a verb+resource statement, so the actual action — retrieve the price history of one product — only becomes clear from the trailing "for one product". An agent can eventually infer the purpose, but it must read through the whole payload inventory to get there. It does implicitly distinguish itself from catalog-search siblings by scoping to a single product.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no sibling is named (e.g. lookup_price for a current-only price, or search_products for discovery). The agent must guess that a required domain+handle pair means this is a per-product lookup, and cannot tell from the text why it would pick this over a cheaper price-only tool.

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