Skip to main content
Glama

Unregistered Short Domains

unregistered_short_domains
Read-onlyIdempotent

Search short .ai, .io, .si, .sh, .so and .md names that were unregistered at the latest data update: 3-letter names and 4-letter names, including CVCV, VCVC, and CCVV shapes (C = consonant, V = vowel), with how many other TLDs each name is registered in. Without a registered account, only .ai names are shown and filters are not available. Not re-checked at query time; confirm with available or bulk_available before registering.

Related: available, bulk_available.

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

Input Schema

NameRequiredDescriptionDefault
tldNoExtension: ai, io, si, sh, so or md. Comma-separate to combine (e.g., 'io,sh'); omit for all.
pageNoPage number, 10 results per page. Page depth depends on your plan.
sortNoSort order
typeNoPattern type filter
excludeNoExclude characters (comma-separated)
keywordNoFilter by characters in prefix
no_hyphenNoExclude hyphens
no_numberNoExclude numbers
tld_countNoFilter by cross-TLD registration count

Output Schema

NameRequiredDescriptionDefault
dataNo
pageNo
errorNo
totalNoNumber of results on this page
successNo
max_pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / required
      Removed value: -[
      -  "success"
      -]
  2. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is largely covered by structured data. Beyond that, the description adds two real behavioral facts: results are not re-checked at query time, and filters/page depth are gated by account plan. Helpful additions, but the staleness and plan-gating are stated once and not elaborated (e.g., no indication of how old the snapshot typically is), so this is solid but not rich.

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 scope, TLD list, and pattern shapes, then caveats, then related tools — a sensible ordering with little waste. The opening sentence is long and stacks many clauses, but every element (TLD list, shape definitions, cross-TLD count) earns its place.

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?

All nine parameters are documented in-schema and an output schema exists, so return-value description is unnecessary. The description covers what an agent needs to call it correctly and interpret results: scope, account gating, staleness, and the verification path.

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 description coverage is 100% with five enums, so the schema already carries the parameter burden and baseline is 3. The description does add meaning to the 'count' dimension by explaining that the attached number is how many other TLDs each name is registered in, but it does not explain the gating of filters by account tier per-parameter or the sort semantics.

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 verb and resource — searching short .ai/.io/.si/.sh/.so/.md names that were unregistered at the latest data update — and pins the scope to 3-letter and 4-letter patterns (CVCV, VCVC, CCVV) with cross-TLD registration counts. It also names the verification siblings (available, bulk_available), so an agent can separate this browse tool from point-check tools without inspecting schemas.

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?

Explicitly says to confirm results with available or bulk_available before registering, which is a clear routing rule to the alternatives. It also states the account-tier condition (unregistered users see only .ai names and cannot use filters), removing the main ambiguity about why results might look truncated.

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.