Skip to main content
Glama

Pricemend return policies

price_history

What a product has cost over the last few months, as far as Pricemend has watched it: the lowest and highest seen, and when the price last moved. Use it to tell someone whether today's price is actually good. Returns empty when nobody has watched that product yet.

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": "price_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
storeYes
productYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does valuable work by disclosing the coverage caveat ('as far as Pricemend has watched it') and the empty-result behavior when a product is unwatched, plus the shape of the returned summary. It stops short of stating that this is a read-only operation, the granularity of the history, or how the window is bounded.

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?

Three short sentences, front-loaded with the resource and return content before the usage hint. The hedge 'as far as Pricemend has watched it' is a little loose but earns its place as a coverage caveat.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only tool with no annotations and no output schema, the description adequately covers what comes back and the empty case. It leaves a real gap around the days parameter and how store/product are identified, which matters given zero schema documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the three parameters are documented only by their bare titles. The description never mentions the days window parameter at all; 'the last few months' only loosely gestures at the 90-day default, and store/product identifier formats are left unaddressed.

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 resource and what it returns: a product's price over the last few months, with the lowest and highest seen and when the price last moved. That is clearly distinct from a single-point lookup like check_price, though it never names the sibling 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?

'Use it to tell someone whether today's price is actually good' supplies one concrete use case, which implies it belongs alongside a current-price check. It gives no when-not guidance and does not name check_price or explain how the two are meant to be combined.

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