Skip to main content
Glama

Trueprice

Price history for a product URL

lookup_price
Read-onlyIdempotent

True price (the lowest price the product really sold at that we know of, from daily checks and archived snapshots: true_price), price history, deal score, best checked promo code and product spec (description, tags, options, SKUs, weights, images) for a product page URL of a Shopify store Trueprice tracks (e.g. https://example.com/products/blue-mug). History (points) starts the day Trueprice first read the product; archived holds earlier prices from archived copies of the store's page (Wayback Machine, since 2025-01), labelled "archived snapshot": snapshots, not daily checks, and not used in the stats or deal score.

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": {
      "url": "<url>"
    },
    "name": "lookup_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe product page URL; a ?variant=<id> in it returns that option's own history

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the baseline is low, yet the description adds real domain behavior: true_price is the lowest price known to have actually sold, history starts at first read, and `archived` comes from Wayback snapshots since 2025-01 that are explicitly excluded from stats and deal score. What is still missing is failure behavior (e.g., a URL not tracked) and freshness/cadence beyond 'daily checks'.

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?

Every clause carries information, but the body is a single wall-of-text sentence that opens with a parenthetical definition of `true_price` rather than the tool's main purpose. The `archived` explanation, which is the most caveat-like content, is buried at the end instead of being front-loaded.

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?

With only one required parameter and no output schema, the description does the work of naming the return fields (`true_price`, `points`, `archived`, deal score, promo code, spec) and their semantics. It falls short only on error/edge behavior and on what `points` look like in volume, which an agent would want before calling.

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% and the single `url` parameter is already documented there, including the `?variant=<id>` behavior and the explicit example URL — so the description mostly restates the schema. Baseline 3 applies; it adds only the qualifier that the store must be one Trueprice tracks.

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 names a specific resource and enumerates what is returned: true price, price history, deal score, best promo code and product spec, scoped to a product page URL of a Shopify store Trueprice tracks. The URL-based scope implicitly separates it from a GTIN lookup sibling, but no sibling is named, so the differentiation is only inferred.

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 context is implied by the data it returns, and the description makes clear it applies only to stores Trueprice tracks, but there is no explicit when-to-use vs. when-to-use-something-else guidance and no statement of what happens for an untracked URL.

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