Deal Radar MCP Server

poll_alerts_now

Triggers a price-drop check across all active watchlist items, so you can confirm current alerts without waiting for the next scheduled poll.

Instructions

Trigger an immediate check across all active watchlist items for price drops.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "poll_alerts_now"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

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 exist, so the description carries the full burden. It discloses scope ('all active watchlist items') but says nothing about whether the call blocks until checks complete, whether it dispatches notifications or persists alert events, whether it is expensive or rate-limited across providers, or what it returns.

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 front-loaded sentence with no filler; the action and the scan scope are both stated immediately.

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 zero-param trigger the call mechanics are covered, but with no output schema and no annotations the agent is left not knowing the response shape or the side effects (notifications, stored results) of firing it.

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?

The tool takes zero parameters and the schema is empty at 100% coverage, so there is no parameter meaning to add. Baseline 4 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?

States a concrete verb-plus-resource: an immediate check across all active watchlist items for price drops. An agent knows exactly what action occurs and over what scope, though it never contrasts itself with siblings such as poll_passive_inventory or start_alert_poller.

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

Usage Guidelines2/5

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

The word 'immediate' hints at an on-demand trigger, but there is no explicit statement of when to call this versus start_alert_poller, check_watchlist, or compare_prices, and no exclusions or preconditions. The agent must infer the routing decision.

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