Skip to main content
Glama
Deal Radar MCP Server

Deal Radar MCP Server

get_price_history

View recorded price history and a fluctuation timeline for a tracked product URL to see how its price has changed over time.

Instructions

View the recorded price history and price fluctuation timeline for a tracked product URL.

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

Input Schema

NameRequiredDescriptionDefault
urlYesProduct URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. 'View' implies a read-only operation, but the description says nothing about the time range covered, the granularity of the history, pagination or size limits, or behavior for untracked or never-polled URLs — all material for a history-retrieval tool with zero annotation coverage.

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?

A single front-loaded sentence with no filler or hedging. 'Price fluctuation timeline' is somewhat redundant with 'price history,' a minor duplication, but nothing is wasted overall.

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

Completeness2/5

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

There is no output schema and no annotations, so the description is the only source of information about what comes back. It never describes the shape of the response (data points, timestamps, series format) or the default time window, leaving significant gaps for a history-query tool.

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?

With a single parameter at 100% schema description coverage, the schema already documents the only input. The description adds one piece of meaning beyond 'Product URL' — that it must be a tracked product — which is genuinely useful but is the only added semantic, so the baseline of 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?

The description names a specific verb ('View') and a specific resource ('recorded price history and price fluctuation timeline') scoped to a tracked product URL, which is far more informative than the bare tool name. It does not explicitly contrast itself with siblings like compare_prices or check_watchlist, so an agent must infer the boundary from the names alone.

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?

The phrase 'for a tracked product URL' implies a prerequisite (the product must already be tracked, presumably via track_product), which is useful implied guidance. However, there is no explicit statement of when to choose this over compare_prices or check_watchlist, and no mention of what happens if the URL is not tracked.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.