Skip to main content
Glama

Save a Drop Radar alert

radar_alert

Save a Drop Radar search and get a signed webhook (event radar.match, header X-StableDomains-Signature = sha256 HMAC of the body with the returned secret) and/or email (double opt-in) when new names match or a pending-delete name drops. Free: 3 alerts per IP, 25 with an API key, max 20 events per alert per day. filters takes the same fields as drop_radar.

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": {
      "filters": "<filters>"
    },
    "name": "radar_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
emailNo
filtersYessame fields as drop_radar (preset, tlds, keywords, max_len, min_quality, ...)
webhook_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Despite annotations already covering the safety profile, the description adds substantial behavioral detail: the `radar.match` event, signed webhook details including the `X-StableDomains-Signature` header and sha256 HMAC with returned secret, email double opt-in, and explicit rate limits (3 per IP, 25 with an API key, 20 events per alert per day).

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?

The description is a single dense but front-loaded sentence with no wasted words. Each clause adds useful information: event name, signature details, double opt-in, limits, and filter compatibility.

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

Completeness4/5

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

For a create-like tool with no output schema and only 25% schema coverage, the description is quite complete regarding webhook signing, email opt-in, rate limits, and filter compatibility. It could be improved by explaining the `name` parameter and whether alerts are updatable or deletable, but the core caller needs are covered.

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 description coverage is only 25%, so the description must compensate. It explains that `webhook_url` produces a signed webhook, `email` uses double opt-in, and `filters` takes the same fields as `drop_radar` including preset, tlds, keywords, max_len, and min_quality; only the `name` parameter is left undocumented, keeping this from a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Save a Drop Radar search'. It makes the persistent-alert purpose clear and implicitly distinguishes this tool from the `drop_radar` sibling, which performs a search rather than saving one.

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

Usage Guidelines4/5

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

The description gives clear context for use: saving an alert to receive webhook or email notifications when new names match or pending-delete names drop. It does not explicitly compare against alternatives such as `watch_domain` or explain when not to use this tool, so it falls short of a 5.

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