Deal Radar MCP Server

set_price_alert

Set a target price alert for an e-commerce product and get notified when its price drops to or below that amount.

Instructions

Set a target price alert on an e-commerce product. Notifies the agent when the price drops to or below target price.

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>",
      "targetPrice": "<targetPrice>"
    },
    "name": "set_price_alert"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	Direct URL to the product page.
`notes`	No	Optional reminder or context (e.g. "Birthday gift for brother")
`targetPrice`	Yes	The target price you want to be alerted at.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 9, 2026

TDQS

A3.6/5.0

Behavior3/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. It usefully discloses the trigger condition ('when the price drops to or below target price') and that the agent is notified, but says nothing about whether the alert persists, fires once or repeatedly, whether a poller must be running, or whether the URL must be a supported store.

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?

Two short sentences, the action stated first and the trigger condition second. There is no filler, hedging, or repetition.

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?

With no annotations and no output schema, the description should explain the alert lifecycle, but it stops at the trigger. For a create-style tool sitting alongside poller and delete siblings, the missing persistence and activation details leave a meaningful gap.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning the schema lacks: it specifies the comparison direction ('drops to or below'), which the targetPrice schema text does not state. The url and notes parameters gain nothing beyond their schema descriptions.

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 and resource ('Set a target price alert') plus the object domain ('an e-commerce product'), which implicitly separates it from set_flight_price_alert. It is clear what the tool does, though it never names a sibling explicitly to sharpen the distinction.

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: 'on an e-commerce product' signals this is the product-flavored alert versus flight alerts, but there is no explicit when-to-use/when-not-to-use guidance, no mention of prerequisites such as tracking the product first, and no pointer to delete_price_alert or the poller tools for lifecycle management.

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