Skip to main content
Glama

Name.ai MCP Server

Search premium domains for sale

search_premium_domains
Read-onlyIdempotent

Search premium domain names for sale on name.ai (domain marketplace): find a domain to buy for a startup, product or brand, with buy-now prices (USD) and a link to each listing, where the purchase happens.

Use when the user wants a name for a startup, product or brand, or wants
to browse domains to buy, optionally within a budget.

`keyword` matches text inside the domain name, so pass ONE short word
("legal", "pay", "health"), not a sentence. For a business idea, call
this several times with different related words, or leave keyword empty
to browse the newest premium names. To check whether one specific domain
is free to register, use search_domain instead.

Backed by GET /api/market/listings (public). Read-only: nothing is bought.

Args:
    keyword: One short word the domain name should contain. Empty = browse.
    tld: TLD without the dot, e.g. "ai" (default) or "com". Empty = any.
    min_price: Lowest buy-now price in USD.
    max_price: Highest buy-now price in USD.
    sort: "newest" (default), "price_asc" or "price_desc".
    limit: Number of results, 1 to 25 (default 10).

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

Input Schema

NameRequiredDescriptionDefault
tldNoai
sortNonewest
limitNo
keywordNo
max_priceNo
min_priceNo

Output Schema

NameRequiredDescriptionDefault
queryYes
totalYes
resultsYes
has_moreYes
browse_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond that: the public GET /api/market/listings backing, USD buy-now prices, a link to each listing, and that the purchase happens at the listing rather than inside this 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?

The description is front-loaded with purpose and usage, then moves to keyword strategy, the alternative tool, endpoint information, and a clear Args list. It is appropriately sized for a 6-parameter tool with no schema descriptions, with only minor redundancy around the read-only nature already declared in annotations.

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?

Given the moderate complexity, six parameters with no schema descriptions, and the presence of an output schema, the description supplies everything an agent needs to call the tool correctly. It covers purpose, when to use, alternative tool selection, all parameter meanings, and the external purchase link, so return values need not be explained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the full burden. It defines every parameter meaningfully: keyword as one short word that matches text inside the domain name, tld without the dot (default 'ai'), min_price/max_price as USD bounds, sort with enum values and default, and limit as 1 to 25 with default 10.

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 states a specific verb and resource: 'Search premium domain names for sale on name.ai', and distinguishes the tool from search_domain by explaining that search_domain checks whether one specific domain is free to register. An agent can identify the exact operation 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use guidance ('Use when the user wants a name for a startup, product or brand, or wants to browse domains to buy, optionally within a budget'), explains keyword strategy ('pass ONE short word', call several times with related words), and names the alternative for a different need (search_domain for availability).

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.