Skip to main content
Glama

Check if a domain is dropping

is_domain_dropping
Read-onlyIdempotent

Is an expired domain about to become available? Returns lifecycle (grace, redemption, pending delete, available, registered), estimated drop date and backlink data if in our drop feed.

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": {
      "domain": "<domain>"
    },
    "name": "is_domain_dropping"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and open-world. The description goes beyond them by disclosing the return shape (lifecycle stages, estimated drop date, backlink data) and the conditional 'if in our drop feed' caveat, which tells the agent results may be partial. No contradiction.

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 tight sentences, front-loaded with the question the tool answers, followed by the concrete return fields. Nothing is redundant.

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?

With no output schema, the description does supply the return fields, and the annotations cover the safety profile, so an agent can call this confidently. It stops short of explaining what happens for a domain outside the feed or how 'estimated drop date' should be interpreted.

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?

There is one parameter with 0% schema description coverage, so the description must carry the load. It implies the input is a domain but never states the expected format (bare domain vs. URL, TLD handling) or error behavior for a non-expired or unknown domain.

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 states a specific check ('Is an expired domain about to become available?') and names the returned lifecycle states, so the resource and operation are unmistakable. It does not, however, distinguish itself from the very similar sibling find_dropping_domains (list search), which leaves one ambiguity.

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 implied by the question phrasing: check a single known domain's drop status. There is no explicit 'use this instead of' guidance against find_dropping_domains, drop_radar, or whois_lookup, and no exclusions or prerequisites are stated.

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