Skip to main content
Glama

check_domains_bulk

Check domain name availability in bulk for up to 50 domains. Uses RDAP lookups to return a summary with total, available, and taken counts per domain.

Instructions

Check availability of up to 50 domain names in one call.

Uses fast RDAP lookups (no pricing). Returns a summary with total/available/taken counts plus per-domain details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainsYesList of domain names to check (max 50).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'check_domains_bulk' tool handler: validates input (max 50 domains), then POSTs the domains to the backend /check endpoint via httpx and returns the JSON response.
    @mcp.tool()
    async def check_domains_bulk(domains: list[str]) -> dict:
        """Check availability of up to 50 domain names in one call.
    
        Uses fast RDAP lookups (no pricing). Returns a summary with
        total/available/taken counts plus per-domain details.
    
        Args:
            domains: List of domain names to check (max 50).
        """
        if len(domains) > BULK_LIMIT:
            return {
                "error": f"Too many domains: {len(domains)} provided, maximum is {BULK_LIMIT}.",
                "limit": BULK_LIMIT,
            }
    
        async with httpx.AsyncClient(base_url=BACKEND_URL, timeout=30) as client:
            resp = await client.post("/check", json={"domains": domains})
            resp.raise_for_status()
            return resp.json()
  • The tool is registered with the FastMCP server via the @mcp.tool() decorator on the async function.
    @mcp.tool()
    async def check_domains_bulk(domains: list[str]) -> dict:
  • The BULK_LIMIT constant (set to 50) is used by the handler to cap the number of domains.
    BULK_LIMIT = 50
  • Input schema: the tool accepts 'domains: list[str]' as the single parameter. Output is a dict as per return type annotation.
    @mcp.tool()
    async def check_domains_bulk(domains: list[str]) -> dict:
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses that lookups are via RDAP and do not involve pricing, and describes the return structure (summary counts and per-domain details). This gives good behavioral insight 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.

Conciseness5/5

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

Two sentences front-load the main purpose, followed by technical detail and return format. No extraneous words; every sentence adds value.

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?

Output schema exists, so description is not required to detail return values. It mentions summary and per-domain details, which is sufficient. Lacks specifics on error handling or input validation, but overall complete for a simple tool.

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?

Input schema has 100% coverage with description for the lone parameter 'domains' (array of strings, max 50). Description reiterates 'up to 50' but adds no new meaning beyond the schema; baseline score of 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?

Description clearly states the verb 'Check availability' and the resource 'domain names', specifying the bulk nature with 'up to 50 domain names in one call'. It distinguishes from the sibling 'check_domain' tool, which is for single 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?

Implies usage for checking multiple domains at once with 'in one call'. Mentions 'Uses fast RDAP lookups (no pricing)' to clarify it's for availability only, not purchasing. No explicit alternatives or when-not-to-use, but context with siblings provides differentiation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nach-dakwale/instadomain-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server