Skip to main content
Glama

suggest_domains

Generate domain name ideas from a keyword and check their availability in real time.

Instructions

Generate domain name ideas from a keyword and check their availability.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordYesA keyword or short business name (e.g. "taskflow").

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The suggest_domains tool handler: an async function decorated with @mcp.tool() that takes a keyword string, calls the backend /suggest endpoint with the keyword as a query parameter, and returns the JSON response containing domain name suggestions with availability info.
    @mcp.tool()
    async def suggest_domains(keyword: str) -> dict:
        """Generate domain name ideas from a keyword and check their availability.
    
        Args:
            keyword: A keyword or short business name (e.g. "taskflow").
        """
        async with httpx.AsyncClient(base_url=BACKEND_URL, timeout=30) as client:
            resp = await client.get("/suggest", params={"keyword": keyword})
            resp.raise_for_status()
            return resp.json()
  • The @mcp.tool() decorator registers suggest_domains as an MCP tool on the FastMCP server instance. The tool is named 'suggest_domains' (the function name) and the docstring serves as its description.
    @mcp.tool()
Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions generating ideas and checking availability, but does not detail what 'check their availability' means (e.g., real-time vs cached), limits on number of suggestions, or any side effects. The description is adequate but minimal.

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 a single sentence that directly communicates the tool's function. It contains no unnecessary words or repetitions, making it highly efficient.

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?

Given the tool has one parameter and an output schema (not shown but indicated), the description is nearly complete. It would benefit from briefly noting the output format (e.g., list of domain names with availability), but current detail is sufficient 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?

Schema coverage is 100% and the description for the keyword parameter is clear. The tool description does not add additional meaning beyond what the schema provides, so 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?

The description clearly states it generates domain name ideas from a keyword and checks availability. It distinguishes from sibling tools like check_domain (single domain check) and check_domains_bulk (bulk check), as well as buy_domain and unlock_domain, by focusing on suggestion rather than verification or purchase.

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?

The description implies usage when needing domain name suggestions from a keyword, but does not explicitly state when to use this tool over siblings like check_domain or buy_domain. No exclusion criteria or alternative recommendations are provided.

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