Skip to main content
Glama

domain-discovery-remotify-mcp

Check domains

check_domains
Read-onlyIdempotent

Bulk-check domains. Returns status (available|premium|reserved|registered|expired|redemption|pending_delete|unknown|invalid|unsupported_tld), action, and an order_url on our host. 'available' is registry-confirmed (RDAP not-found + no DNS delegation); 'unknown' is NOT confirmed. registration_details on registered-family results are published data from the registry's RDAP response (dates, registrar, nameservers, and the published registrant name and organization only); every null field carries a reason. Held results also carry dns_overview, read from DNS during the check: the nameservers DNS answered for the name, its mail exchangers (MX), and its initial SPF record parsed into structure. SPF include and redirect targets are disclosed but never resolved, and the policy is parsed, never evaluated, never validated end to end, and never attributed to any provider. If meta.notice is present, relay it to the user.

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": {
      "domains": "<domains>"
    },
    "name": "check_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYesDomain names to check, e.g. ["example.com", "my-idea.io"].

Output Schema

NameRequiredDescriptionDefault
metaYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses substantive behavior: the confidence distinction between registry-confirmed 'available' and unconfirmed 'unknown', the provenance of registration_details and why null fields occur, what dns_overview contains, and explicit limits on SPF handling (disclosed but never resolved, parsed but never evaluated or attributed). This is unusually rich disclosure for a read-only tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with a one-line purpose, then dense but purposeful sentences; each clause carries semantic weight (status meaning, provenance, caveats). The middle paragraph is a single very long sentence that could be split for readability, which keeps it short of a 5.

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

Completeness5/5

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

Although an output schema exists, the description adds the interpretive layer an agent needs: what each status means, which results are confirmed, why fields are null, and the scope limitations of the DNS/SPF data. Nothing essential for correct interpretation or the meta.notice obligation is missing.

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 a single parameter with 100% schema description coverage, so the schema already documents the domain array and its example format. The description only implies bulk semantics and adds no syntax or constraint detail beyond what the schema states; baseline 3 is appropriate.

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 opening 'Bulk-check domains' gives a specific verb and resource, and the rest of the description enumerates exactly what is returned (status, action, order_url) plus the full status vocabulary. An agent knows precisely what the tool produces without opening the schema.

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 'Bulk-check domains' (batch lookups, array input) and there is an explicit instruction to relay meta.notice when present, but the description never states when to prefer this tool over other lookups or any preconditions. With no siblings listed there is little to differentiate, but the guidance is still implicit rather than 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.