Skip to main content
Glama

Pagetool

Domain search

domain_search
Read-onlyIdempotent

Checks availability and price for a domain, or for a bare name across a set of TLDs. Free and needs no account. Use it once the user wants their finished draft on a real address. A refused or unchecked domain ending carries reason and a plain reason_text: unsupported or price_unavailable mean we do not sell that ending right now; lookup_failed or cap_reached mean it was NOT checked, so search again, and never tell the customer we do not sell it.

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

Input Schema

NameRequiredDescriptionDefault
tldsNoComma-separated TLDs to check a bare name against, e.g. "com,io". Ignored when query is a full domain.
limitNoMax number of results to return (default: all, max 25).
queryYesA full domain (name.tld) or a bare name to check across TLDs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description still adds substantial operational context: no account or cost required, and a precise decoding of refusal reasons. It separates 'we do not sell that ending' (unsupported, price_unavailable) from 'it was not checked' (lookup_failed, cap_reached) and instructs the agent to retry rather than report non-availability, which is behavior an agent could not infer from annotations alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each doing distinct work: what it does, when to use it, and how to interpret failures. The capability statement is front-loaded and the longer error-handling sentence is justified by consequence, with no 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?

With no output schema, the description commendably documents the refusal payload (reason, reason_text) and how to act on each code. It does not describe what a successful result contains (availability flag and price shape), which is the one remaining gap for an agent that must relay results to a customer.

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 the schema already documents query, tlds and limit, including that tlds is ignored for a full domain. The description restates the bare-name-across-TLDs behavior but adds no new syntax, default, or constraint meaning beyond the schema, so 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 verb and resource ('Checks availability and price for a domain') plus the bare-name-across-TLDs variant. It is immediately distinguishable from the sibling purchase/registration tools (domain_register, prowess_buy_domain) because it is explicitly framed as a lookup that is free and needs no account.

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 a clear trigger condition: 'Use it once the user wants their finished draft on a real address.' This tells the agent when in the workflow to call it. It stops short of naming an exclusion (e.g., 'do not use to purchase'), so it is strong context rather than a full when/when-not/alternatives statement.

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