Skip to main content
Glama

Gợi ý tên miền còn trống

cloud_domain_suggest
Read-onlyIdempotent

Generate available domain name suggestions from a keyword, with VND prices and real availability checks. Handles Vietnamese diacritics and prioritizes industry-specific extensions.

Instructions

Gợi ý những tên miền còn trống quanh một từ khoá, kèm giá VND đã gồm VAT. Từ khoá nhận tiếng Việt có dấu, tool tự bỏ dấu thành nhãn hợp lệ. Truyền industry (slug từ cloud_domain_tld_groups) để ưu tiên đuôi hợp ngành — vd quán cà phê sẽ ra .cafe và .coffee trước. Mọi kết quả đều đã tra trạng thái thật tại nhà đăng ký. Dùng khi tên người dùng muốn đã có người lấy, hoặc khi họ chưa nghĩ ra tên. Sau khi người dùng chọn thì gọi cloud_domain_buy (hoặc cloud_domain_reserve nếu chưa đăng nhập). Không cần đăng nhập.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoSố gợi ý trả về. Mặc định 12.
keywordYesTên muốn đặt hoặc từ khoá mô tả sản phẩm (vd: "Cà Phê Sạch", "myapp").
industryNoSlug ngành từ cloud_domain_tld_groups để ưu tiên đuôi hợp ngành.
include_takenNotrue = giữ lại cả tên đã có người đăng ký.
max_price_vndNoChặn trần giá năm đầu.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/open-world safety. The description adds real behavioral context beyond them: diacritic auto-stripping, live registrar status checks, VAT-inclusive VND pricing, and 'no login required'. Return format is not described, but annotations lower the bar.

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 purpose then usage, next step, and auth note; each sentence carries information. Slightly dense but no obvious filler.

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?

For a read-only suggestion tool with no output schema, the definition covers purpose, when to use, next actions, and auth requirements. Minor gap: no description of the result shape or how many/which TLDs are considered.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description goes beyond the schema by explaining industry as a slug from cloud_domain_tld_groups that biases TLD selection (coffee → .cafe/.coffee) and clarifying that keyword accepts accented Vietnamese.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: suggests available domains around a keyword, with price info. It clarifies scope (around a keyword) and names downstream siblings (cloud_domain_buy/reserve), though it does not explicitly contrast with cloud_domain_search.

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 clear triggering conditions: use when the desired name is taken or the user hasn't thought of one, and specifies the follow-up call. It lacks an explicit 'do not use for X' exclusion relative to cloud_domain_search, so it falls just short of 5.

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

Deploy Server

Other Tools