Skip to main content
Glama

vet_price

Read-onlyIdempotent

Judge a USD price for one product. Returns verdict (good, fair or high; null when there is nothing to compare it with), action (buy_now, wait, compare or null), reason (the basis, in one or two sentences) and products (the listings the reason cites: title, store, price, the matched variant, every variant with its price, url). high with compare: another store sells the same item for at least $1 and 5% less; high with wait: above its usual price of the past year. Same item: a stated size or pack count must match; unstated ones may differ. When the same item has no other store's price and no price history, the verdict compares it with similar listings and the reason says which; such a verdict compares different products. When the product is not identified, products are the top listings meeting the request; use their links for a specific judgment. Relay the reason and links; do not invent prices.

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": {
      "product": "<product>"
    },
    "name": "vet_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNoOptional; accepted for compatibility and not used.
priceNoOptional total USD price to evaluate for the entire quantity, excluding tax and shipping. Supply the final amount to assess; do not multiply it by quantity.
productYesProduct URL, ASIN, GTIN, product or offer ID, or a name with its known specifications (size, pack count). Pass URLs and IDs alone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / product / description
      Previous value: -"Product URL, ASIN, GTIN, product or offer ID, model name, or description including known specifications. Pass URLs and IDs alone, without appended requirements."New value: +"Product URL, ASIN, GTIN, product or offer ID, or a name with its known specifications (size, pack count). Pass URLs and IDs alone."
    • changedInput schema / properties / unit / description
      Previous value: -"Optional total quantity covered by price, e.g. {\"quantity\":1000,\"unit\":\"ml\"} for two 500 ml bottles. For consumables or multi-packs, provide the known total quantity here when possible. It may also be identified from the product description or linked product data. Do not guess an unknown quantity."New value: +"Optional; accepted for compatibility and not used."
  2. Changed2 schema fields changed
    • addedInput schema / properties / product / maxLength
      Added value: +2000
    • addedInput schema / properties / product / minLength
      Added value: +1
  3. Changed5 schema fields changed
    • changedInput schema / properties / price / description
      Previous value: -"USD price the shopper sees, before coupons, tax and shipping. When omitted, a resolved exact offer can supply its price; otherwise no purchase verdict is available."New value: +"Optional total USD price to evaluate for the entire quantity, excluding tax and shipping. Supply the final amount to assess; do not multiply it by quantity."
    • changedInput schema / properties / product / description
      Previous value: -"One product URL, ASIN, GTIN, product ID, model number or short description. Pass URLs and IDs alone, without appended requirements. For descriptions, include product type and known specs. Products outside the catalog can still be judged."New value: +"Product URL, ASIN, GTIN, product or offer ID, model name, or description including known specifications. Pass URLs and IDs alone, without appended requirements."
    • changedInput schema / properties / unit / description
      Previous value: -"The total quantity covered by price. Optional for single items (one TV, one drill), which default to 1. Needed for measured goods priced by volume, weight or count, e.g. {\"quantity\":96,\"unit\":\"load\"} or {\"quantity\":1000,\"unit\":\"ml\"} for two 500 ml bottles. For an exact offer ID, URL or ASIN without it, that offer's quantity is used."New value: +"Optional total quantity covered by price, e.g. {\"quantity\":1000,\"unit\":\"ml\"} for two 500 ml bottles. For consumables or multi-packs, provide the known total quantity here when possible. It may also be identified from the product description or linked product data. Do not guess an unknown quantity."
    • changedInput schema / properties / unit / properties / quantity / description
      Previous value: -"Total amount of product covered by price; must be greater than zero."New value: +"Total quantity covered by price; greater than zero."
    • changedInput schema / properties / unit / properties / unit / description
      Previous value: -"Unit of measure for quantity, such as ml or item; must be convertible to the product pricing unit."New value: +"Unit of measure for quantity, such as ml, g, count or item."
  4. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Despite the annotations covering safety and idempotency, the description adds substantial behavioral detail: exact verdict and action values, rules for 'high with compare' and 'high with wait', matching requirements for size or pack count, fallback comparison behavior, and a warning not to invent prices. This is far beyond what the annotations provide.

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 description is front-loaded with the core purpose and return shape, then moves into decision rules and edge cases. It is dense but every sentence carries operational meaning, with only minor room for tighter structuring.

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 and only read-only/idempotent annotations, the description carries the burden of explaining returns and does so well: verdict, action, reason, and product listing fields. A few details are omitted, such as behavior when the optional price is not supplied and any limits on returned products.

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 the parameters are already fully documented. The description adds useful context about product matching and comparable items, but it does not add parameter-specific meaning beyond the schema.

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 states a specific action and resource: judging a USD price for one product, with verdicts and actions. It is clearly distinct in substance from search/find tools, but it does not explicitly name or differentiate itself from any sibling tool.

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?

It explains how verdicts are formed and what to do when the product is not identified, which implies when the tool is appropriate. However, it gives no explicit when-to-use or when-not-to-use guidance relative to alternatives such as find_deals or search_products.

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