Lookup-Domain
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XBY_APIKEY | Yes | 你的实际apikey (Your actual API key) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| domain_lookupA | Look up domain information using RDAP protocol with WHOIS fallback. Provides comprehensive domain registration details, nameservers, contacts, and status information. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools, as there are no other tools to compare it against. The tool's purpose is clearly defined and singular.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'domain_lookup' follows a clear verb_noun pattern, but there are no other tools to assess consistency across a set.
A single tool is generally too few for most server purposes, as it limits functionality and can indicate a thin or incomplete surface. For a domain lookup server, basic operations like checking availability or historical lookups might be missing, making the scope feel underdeveloped.
The tool provides comprehensive domain lookup, but the server's purpose likely extends beyond a single lookup operation. Obvious gaps include no tools for domain availability checks, bulk lookups, historical data, or management actions, which are common in domain-related services.