Skip to main content
Glama

Pricemend return policies

check_price

What a product costs on a retailer's site right now. Takes a product link, or a model or article number for the stores that have one indexed. Only works for stores whose policy record says price_checkable is true; the rest block automated requests and will return an error saying so.

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

Input Schema

NameRequiredDescriptionDefault
storeYes
productYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose a key failure mode: non-price_checkable stores block automated requests and return an explanatory error. It omits rate limits, authentication expectations, and what a successful response contains.

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

Conciseness5/5

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

Three short sentences, front-loaded with the core purpose, followed by accepted input forms and then the eligibility constraint. No filler or repetition.

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 two-parameter, no-output-schema tool, this covers purpose, input flexibility, and a blocking precondition. The remaining gap is the 'store' parameter format and where an agent would learn a store's price_checkable status.

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 0%, so the description must compensate. It does clarify that 'product' accepts a link, model number, or article number, which is genuinely useful, but 'store' is left unexplained — whether it takes a name, ID, or URL is never stated.

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: retrieving the current price of a product on a retailer's site. The phrase 'right now' implicitly distinguishes it from the sibling price_history tool, though it never names that alternative outright.

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

Usage Guidelines4/5

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

Gives a concrete precondition (the store's policy record must have price_checkable set to true) and explains what happens otherwise. It does not explicitly direct the agent to coverage or store_policy for checking eligibility, so the routing to siblings is left implicit.

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