Skip to main content
Glama

Search a name across endings

search_name
Read-onlyIdempotent

Checks one name across many endings at once: com, net, org, io, co, ai, app, dev, xyz, me, info and co.uk, or the endings given. Free names come first, cheapest first. Each result has domain, available (true, false or null), status (available, taken or unknown), checked_at, confirmed and by (registry, registrar, dns, dns_only or confirming); confirmed=false means the answer came from DNS and is still being confirmed. A free domain has price (first_year, renews, min_years, currency USD) and buy_url, a link to register that domain at a registrar. A taken domain has registrar, registered and expires when the registry publishes them.

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": {
      "name": "<name>"
    },
    "name": "search_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe name without an ending, such as brightfield
endingsNoOptional endings to check, such as ["com", "io", "co.uk"]

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?

Beyond annotations, the description discloses ordering behavior, result statuses, the meaning of confirmed and by, and how free versus taken domains differ. This gives an agent substantial behavioral context for interpreting results correctly.

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 purpose is front-loaded and most content is useful, especially because there is no output schema. It is somewhat dense and packs multiple return-field explanations into one paragraph, but it avoids obvious fluff.

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?

With no output schema, the description carries the burden of explaining return values and does so thoroughly, including availability, status, confirmation state, pricing, and registrar details. It is complete for a read-only domain availability search.

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 already 100%, so the schema handles parameter documentation. The description adds useful default-ending behavior and clarifies that name excludes the ending, which goes beyond the structured schema.

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?

The description states a specific verb and resource: checks one name across many domain endings. It is clear about scope and output, but it does not explicitly distinguish itself from siblings such as check_domains.

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?

Usage is implied by the default ending list and the ability to pass custom endings, but there is no explicit when-to-use guidance or comparison with alternatives like check_domains or domain_details.

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