Deal Radar MCP Server

add_store_adapter

Register a new e-commerce site using CSS selectors and a search URL template so the agent can search products and track prices.

Instructions

Dynamically register a new e-commerce website with declarative CSS selectors so the agent can track prices on it.

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": {
      "id": "<id>",
      "name": "<name>",
      "domains": "<domains>",
      "searchUrlTemplate": "<searchUrlTemplate>",
      "selectors": "<selectors>"
    },
    "name": "add_store_adapter"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Unique slug ID for the store (e.g., "croma")
`name`	Yes	Display name (e.g., "Croma")
`domains`	Yes	Domains handled by this store (e.g., ["croma.com"])
`selectors`	Yes	CSS selector map for extracting data
`currencyCode`	No	Currency code like "INR", "USD"
`searchUrlTemplate`	Yes	Search URL with {query} placeholder (e.g., "https://www.croma.com/searchB?q={query}")

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 9, 2026

TDQS

B3.2/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, and it discloses very little. 'Dynamically register' implies a runtime mutation of persistent configuration, yet the description does not say whether the registration survives restarts, whether it overwrites an existing adapter with the same id, what happens on invalid selectors, or whether live pollers pick up the change.

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?

A single well-formed sentence with the action front-loaded and no filler. Every clause earns its place by contributing mechanism or motivation.

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?

This is a mutation tool with five required parameters including a nested object of nine CSS selectors and no output schema, so the description should do more than one sentence. It omits persistence, idempotency/override behavior, validation failure modes, and any indication of what a successful registration returns.

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 every parameter and every nested selector field is already documented in the schema, establishing a baseline of 3. The description adds no meaning beyond that — it does not explain selector granularity, when the optional selectors like searchRating or productOriginalPrice matter, or the relationship between domains and searchUrlTemplate.

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 ('register a new e-commerce website') and adds the mechanism ('declarative CSS selectors') plus the payoff ('so the agent can track prices on it'). It is clearly distinguishable from read-oriented siblings like list_supported_stores, though it does not name the closest alternative 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?

The trailing clause implies the motivating situation (a store you want price tracking on), but there is no explicit when-to-use or when-not-to-use guidance. It never tells the agent to check list_supported_stores first, nor what to do when a store with the same id already exists.

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