Skip to main content
Glama

Trueprice

Same product by barcode

lookup_gtin
Read-onlyIdempotent

Every tracked Shopify listing with this barcode (GTIN / UPC / EAN), across stores: domain, handle, title, price and stock of that option, and its Trueprice URL. Barcodes come from the stores' own product data; coverage grows as products are read.

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": {
      "gtin": "<gtin>"
    },
    "name": "lookup_gtin"
  }
}

Input Schema

NameRequiredDescriptionDefault
gtinYes8, 12, 13 or 14 digits (UPC-A, EAN-13, GTIN-14)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds genuine value by disclosing that barcodes come from the stores' own product data and that coverage grows as products are read, warning that an empty result may reflect missing data rather than a nonexistent product. It stops short of stating result caps or ordering for large match sets.

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?

Two sentences, front-loaded with the scope ('Every tracked Shopify listing with this barcode'), then the return payload, then the coverage caveat. Dense but no filler; the only mild cost is a colon-delimited field list that reads as a run-on.

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 no output schema, the description correctly compensates by enumerating the returned fields and the cross-store scope, plus the data-coverage caveat. Missing only details on result limiting/pagination for products carried in many stores, which matters given the 'every listing' claim.

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 coverage is 100% and the schema already specifies accepted lengths (8/12/13/14) and symbologies (UPC-A, EAN-13, GTIN-14). The description's mention of 'GTIN / UPC / EAN' largely restates that, adding only the colloquial aliasing, so baseline 3 applies.

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 resource and matching key: every tracked Shopify listing with this barcode across stores, and even enumerates the returned fields (domain, handle, title, price, stock, Trueprice URL). It is unambiguous what the tool does, though it never names a sibling (e.g. lookup_price or lookup_price vs search_products) to draw the boundary explicitly.

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 only implied: an agent must infer that this is the tool for exact barcode identification rather than name search. There is no explicit when-to-use/when-not statement and no pointer to alternatives such as search_products for non-barcode lookups.

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