Skip to main content
Glama

domainsdb_search

Read-onlyIdempotent

Search registered domain names by keyword or pattern, optionally filtering by TLD zone and result limit, to find matching domains for research or availability checks.

Instructions

Search registered domain names by keyword or pattern.

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

Input Schema

NameRequiredDescriptionDefault
zoneNoTLD zone filter (e.g. 'com', 'org', 'io').
limitNoMax results (default 20).
domainYesDomain keyword to search (e.g. 'google', 'shop').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds nothing beyond the purpose statement – no result limits (beyond schema's default), no pagination, no rate-limit or pattern-syntax behavior. With annotations doing the heavy lifting, a 2 for the description's marginal contribution is fair.

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?

A single front-loaded sentence with zero waste. It's appropriately sized for a simple search tool, though the phrase 'or pattern' is left unexplained, so some ink is spent on an unelaborated concept.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only search tool with full schema coverage, complete annotations, and no output schema, the description is minimally adequate. It leaves open what 'pattern' means and what a result contains, but the structured fields cover most of what an agent needs to invoke it.

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 each parameter (domain, zone, limit) documented inline, so baseline is 3. The phrase 'keyword or pattern' loosely hints at domain-param format but doesn't clarify wildcard/pattern syntax that the schema doesn't cover.

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 ('Search registered domain names') and adds the query mode ('by keyword or pattern'). It doesn't explicitly distinguish itself from the only related sibling, domainsdb_tlds, but the collision risk is low since that tool enumerates TLDs rather than searching them.

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 purpose ('search ... by keyword or pattern') but there's no explicit when-to-use guidance, no mention of when to prefer domainsdb_tlds versus this, and no prerequisites stated. An agent can infer the use case but gets no routing help.

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