Skip to main content
Glama

Suggest available names

suggest_names
Read-onlyIdempotent

Drafts domain names for a business, brand or project from a short description, checks each one, and returns only names that were free to register when checked: each with the reason it fits, price (first_year, renews, min_years, currency USD), confirmed, by and buy_url, a link to register that domain at a registrar. confirmed=false means very likely free and still being confirmed. Takes 10 to 20 seconds.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "brief": "<brief>"
    },
    "name": "suggest_names"
  }
}

Input Schema

NameRequiredDescriptionDefault
briefYesWhat the business or project is, in a few words, such as "a yoga studio in Chiang Mai"
countNoHow many names, 6 when left out

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly, openWorld, idempotent and non-destructive, yet the description still adds substantive behavior: results are pre-filtered to names free at check time, confirmed=false means 'very likely free, still confirming', and the call takes 10-20 seconds — a latency budget the agent needs for planning. It also enumerates the return payload (price breakdown, confirmed, by, buy_url).

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 what the tool does and its filtering guarantee, with the latency note at the end. The middle field-list sentence is dense and runs long, but every listed field and the confirmed=false caveat carries real decision value, so little is wasted.

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?

With no output schema, the description carries the return-value burden and does so: field names, price sub-fields, the confirmed flag semantics, and a usable buy_url. The only gap is the absence of any hint about how results are ordered or whether count caps the confirmed-only set.

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%, so both brief and count are fully documented in the schema, including the default of 6 and the maximum of 10. The description only restates that the input is 'a short description' and never mentions count, so it adds little beyond the structured fields — 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 compound verb chain and resource: drafts domain names from a brief, checks each, and returns only the free ones. That generate-check-filter pipeline is distinctive enough that an agent can separate it from check_domains or search_name without opening a schema.

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 trigger condition is implied — you have a business/project description and want candidate names — but there is no explicit when-to-use versus check_domains (already have names) or search_name (searching by keyword), and no exclusions or prerequisites stated.

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.

Resources