Skip to main content
Glama
universal-mcp

domain-checker

by universal-mcp
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Server Quality Checklist

67%
Profile completionA complete profile improves this server's visibility in search results.

  • Latest release: v0.1.1

  • Disambiguation5/5

    The two tools have clearly distinct purposes: one checks a specific domain's availability, and the other checks a keyword across multiple TLDs. No overlap.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern with the 'check_' prefix and a common '_tool' suffix, making the naming predictable.

    Tool Count3/5

    With only 2 tools, the set feels thin for a domain checker, but it covers the core use cases of checking a single domain and exploring multiple TLDs.

    Completeness3/5

    The tools cover basic domain availability checking and keyword search across TLDs, but lack additional operations like detailed WHOIS lookups or bulk checks, leaving notable gaps.

  • Average 3.2/5 across 2 of 2 tools scored.

    See the Tool Scores section below for per-tool breakdowns.

    • No community issues in the last 6 months
    • 0 commits in the last 12 weeks
    • No stable releases found
    • No critical vulnerability alerts
    • No high-severity vulnerability alerts
    • No code scanning findings
    • CI status not available

  • This repository is licensed under MIT License.

  • This repository includes a README.md file.

  • No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.

    Tip: use the "Try in Browser" feature on the server page to seed initial usage.

  • Add a glama.json file to provide metadata about your server.

  • If you are the author, simply .

    If the server belongs to an organization, first add glama.json to the root of your repository:

    {
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}

    Then . Browse examples.

  • Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

  • Behavior2/5

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

    With no annotations provided, the description carries the full burden of behavioral transparency. It states the tool checks 'across multiple TLDs' but gives no details on which TLDs, how availability is determined, or any side effects (e.g., rate limits, caching). This minimal disclosure is insufficient for an agent to understand the tool's full behavior.

    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?

    The description is a single sentence that is front-loaded with the core action ('Checks a keyword across multiple TLDs') and includes the outcome ('find available domain names'). Every word is necessary and there is no redundancy or filler.

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

    Completeness2/5

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

    Given the simplicity of this tool (one parameter, no output schema) and the presence of a sibling, the description should explain what 'available' means, whether there are limitations on TLDs checked, and how results are returned. The current description leaves significant gaps, making it incomplete for an agent to use effectively without additional context.

    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%, so the baseline is 3. The parameter 'keyword' already has a clear description in the schema ('String representing the keyword to check across TLDs (e.g., "myapp")'). The tool description adds no new semantic information beyond what is in the schema, thus it does not improve the baseline.

    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?

    The description clearly states the tool checks a keyword across multiple TLDs to find available domains, using a specific verb and resource. However, it does not explicitly differentiate from the sibling tool 'domain-checker_check_domain_tool', which likely checks a specific domain rather than a keyword across TLDs. A brief contrast would elevate it to 5.

    Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

    Usage Guidelines2/5

    Does the description explain when to use this tool, when not to, or what alternatives exist?

    No guidance is provided on when to use this tool versus the sibling 'domain-checker_check_domain_tool'. The context signals list the sibling but the description lacks any mention of scenarios where one should prefer this tool over the other, leaving the agent without decision criteria.

    Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

  • Behavior3/5

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

    Mentions the method of checking (DNS and RDAP), which provides some behavioral context. However, no annotations exist, and the description does not disclose potential costs, rate limits, or whether the operation is truly read-only beyond what is implied. Bare minimum transparency for a simple check tool.

    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?

    Single sentence, 15 words, no wasted words. Efficient and direct, but could be slightly improved by front-loading the core purpose more prominently (though it already does).

    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?

    Adequate for a simple tool with one parameter and no output schema, but fails to describe the return format or error conditions. The agent does not know if the response is boolean, string, or structured, which is a gap given the complexity level.

    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?

    The input schema already provides a clear description of the single parameter 'domain'. The tool description adds no additional meaning beyond what is in the schema. Baseline 3 due to 100% schema coverage.

    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?

    Clearly states the verb 'checks' and resource 'domain availability', distinguishing from sibling tool 'check_tlds_tool' by specifying it checks domains for registration availability. The description is specific and actionable.

    Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

    Usage Guidelines2/5

    Does the description explain when to use this tool, when not to, or what alternatives exist?

    No guidance on when to use this tool versus the sibling 'check_tlds_tool'. Lacks any contextual instructions about prerequisites, domain format restrictions, or when to prefer alternative tools.

    Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

  • Confirm that the MCP server is working as expected.
  • Confirm that there are no obvious security issues.
  • Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

domain-checker MCP server

Copy to your README.md:

Score Badge

domain-checker MCP server

Copy to your README.md:

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/universal-mcp/domain-checker'

If you have feedback or need assistance with the MCP directory API, please join our Discord server