Skip to main content
Glama
Internamaro Apify Data MCP

Internamaro Apify Data MCP

Check Domain Availability

check_domain_availability
Read-only

Determine whether domain names are registered or available using RDAP and DNS, and optionally retrieve registrar and expiry details for up to 1,000 domains per call.

Instructions

Returns one item per domain with domain, available (true, false or null when unknown), status, tld, checkedAt and error; registrar and dates too when details is true. Checks whether domain names are registered or available, using RDAP registry data and DNS. Up to 1,000 names per call. Do not use it to register other people's trademarks. Give at least one of: domains. Runs the Apify Actor ucchiii/domain-availability-api on YOUR Apify account (APIFY_TOKEN); you pay that Actor's pay-per-event price, see https://apify.com/ucchiii/domain-availability-api.

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

Input Schema

NameRequiredDescriptionDefault
detailsNoOff (default): each row has only domain, available, status, tld, checkedAt and error. On: rows also carry the registrar, its IANA ID, created / updated / expiry dates, days to expiry, registry status codes, nameservers and how the answer was decided. Same price either way.
domainsNoDomain names to check, e.g. 'example.com'. Send them as a JSON array from code. URLs ('https://www.example.com/page') are cut down to the host name, letters are lowercased, internationalized names (münchen.de) become punycode and duplicates are removed. Up to 1,000 names per run.Do not use this Actor to register names that contain someone else's trademark or brand (cybersquatting) or for impersonation.
concurrencyNoHow many names are checked in parallel. Allowed range 1 to 25 (default 10). Whatever you set, at most 2 connections go to one registry server at a time, with at least 0.25 s between requests to the same server, so a long list in one TLD is paced by that registry.
timeoutSecsNoTimeout for each request, in seconds (default 5, range 1 to 60). Failed requests (rate limits, server errors, timeouts) are retried up to 3 times with a growing pause; a name that still gets no answer comes back unknown and is not charged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations declare only readOnlyHint and openWorldHint; the description goes well beyond by disclosing cost ('you pay that Actor's pay-per-event price'), account/auth requirement, the unknown-value semantics, the fact failed names are uncharged, and retry behaviour. This is exactly the kind of economic and failure-mode context annotations cannot carry.

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-loads the return shape and purpose, and every sentence carries either data-source, limit, cost, or policy information. It is dense and slightly run-on (a long semicolon-chained first sentence plus a repeated 1,000-name cap), which costs a point.

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?

No output schema exists, so the description must and does enumerate return fields including the tri-state 'available' value and the error field. With auth, pricing, limits, retry and uncharged-unknown behaviour also covered, an agent has everything needed to call it correctly.

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?

Schema description coverage is 100%, so every parameter is already documented richly in the schema itself, including normalisation rules and concurrency pacing. The description only restates the 'details=true adds registrar and dates' and 'up to 1,000' behaviour, adding little beyond the schema; the baseline 3 applies.

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?

States a specific verb and resource ('Checks whether domain names are registered or available') plus the data sources (RDAP registry data and DNS), and the first sentence pins down the exact per-domain return shape. The tool is unmistakably distinct from the sibling utilities (json/excel/html helpers).

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?

Gives operational context an agent needs before calling: up to 1,000 names per call, at least one of 'domains' will be supplied, it runs on the caller's Apify account via APIFY_TOKEN with pay-per-event pricing, and it names prohibited uses (trademark registration/impersonation). It does not name or contrast against an alternative availability checker, so it stops short of full 5-level routing guidance.

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