Skip to main content
Glama

HokuHost Domains

search_domains

Read-only

Live availability + yearly price (renewal same). Letters are never changed for you: a name with accents, www., a subdomain or other characters is refused with a suggestion; only spaces and capitals are dropped, and the checked name comes back as name. status: available | taken | premium_not_offered | not_allowed | not_offered_now | unknown (retry later).

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_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYese.g. pixelstudio or pixelstudio.io
tldsNoe.g. ["com","io"]; default: 10 popular

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, the description discloses non-obvious behavior: accent/www./subdomain inputs are refused with a suggestion, only spaces and capitals are dropped, the checked name is echoed back, and the full status enum with meanings is given. This is exactly the kind of normalization and outcome detail annotations cannot convey.

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?

Dense and largely front-loaded, with the core capability first and normalization/status details after. It reads as a run-on with semicolons rather than distinct sentences, but almost every clause carries substantive information.

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 only two params and no output schema, the description covers input normalization, availability status values, and pricing semantics well. It never states the returned shape beyond 'name' and price, but for a simple search tool this is largely complete.

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 100%, so baseline is 3, but the description adds real meaning: what forms of the name are accepted or transformed and that the normalized name is returned. The tlds default is already in the schema, so it isn't duplicated.

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?

Front-loaded 'Live availability + yearly price (renewal same)' states a specific verb and resource, and the status list makes clear it returns availability. It doesn't explicitly differentiate itself from siblings like get_domain or get_prices, so a 4 rather than 5.

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 (search for availability/pricing of a candidate name), and the status semantics hint at retry behavior via 'unknown (retry later)'. However, there is no explicit when-to-use vs. get_domain/get_prices guidance or exclusion criteria, leaving the agent to infer.

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