Skip to main content
Glama

Domain Drop Radar search

drop_radar
Read-onlyIdempotent

Domain Drop Radar: expiring, pending-delete and just-dropped domains filtered by TLD(s), length, keywords, value, quality and drop date, with presets (short-brandable, ai-names, dictionary-com, real-history, cheap-good, dropping-this-week). Returns a summary plus the top 25 with quality reasons, est. value, price, and a ready create_order body for available names or a watch body for others. For up to 500 rows call GET /api/v1/drops/full via x402 ($0.01). Page with limit + cursor (next_cursor in the response); sort with sort + order. To be alerted on future matches call radar_alert.

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

Input Schema

NameRequiredDescriptionDefault
sortNo
tldsNo
limitNomax 25 on the free tier
orderNosort direction; default depends on sort
cursorNonext_cursor from the previous call
presetNo
statusNo
max_lenNo
min_ageNo
min_lenNo
keywordsNo
ends_withNo
max_priceNo
max_valueNo
min_valueNo
no_digitsNo
no_hyphenNo
dictionaryNo
min_qualityNo
starts_withNo
available_onlyNoonly names registrable now
new_within_hoursNo
drops_within_daysNopending-delete names dropping within N days

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/destructive annotations, the description discloses concrete behavior: free-tier returns summary plus top 25, up to 500 rows are available through a paid x402 endpoint, pagination uses cursor/next_cursor, and results include quality reasons, estimated value, price, and create_order/watch bodies. This is unusually rich behavioral context for an agent.

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 dense but front-loaded and purposeful: scope, return shape, paid full-result option, pagination, and alert alternative are each covered in one place. Given the tool's complexity, every sentence earns its place.

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 complex 23-parameter tool with no output schema, the description does well on return shape, paging, and alert routing, but it is not complete enough on parameter semantics. An agent can understand the tool's overall behavior but would still need to guess the meaning of many filters.

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

Parameters2/5

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

Schema description coverage is only 22% across 23 parameters, so the description must compensate and largely does not. It names broad filter categories and paging/sort mechanics, but leaves many parameters such as min_age, no_digits, no_hyphen, dictionary, starts_with, ends_with, max_price, available_only, new_within_hours, and drops_within_days without semantic explanation.

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 gives a specific verb and resource: a Drop Radar search over expiring, pending-delete, and just-dropped domains, with named filters and presets. It distinguishes the alerting sibling radar_alert, but does not explicitly differentiate this search from other domain-search siblings such as find_dropping_domains.

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?

It clearly indicates the search context and explicitly routes future-match alerting to radar_alert. It also explains the paid full-result path and paging mechanics, though it does not state when to choose this over sibling search tools like search_domains or find_dropping_domains.

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