Skip to main content
Glama
Sign In
mcp-namecheap

mcp-namecheap

by fantomdancer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

namecheap_get_domain_info

Retrieve full details for any domain: owner, status, creation and expiry dates, DNS provider, and nameservers.

Instructions

Get detailed info about a domain: owner, status, creation/expiry dates, DNS provider, nameservers.

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": "namecheap_get_domain_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name (e.g. "example.com")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It describes a read operation ('Get') and specifies the data fields returned, but it does not disclose potential side effects, authentication requirements, rate limits, or error behavior. It adds some context but not deep behavioral transparency.

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?

One concise sentence with a clear verb and a list of returned data. No filler or repetition, front-loaded with the action.

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

Completeness5/5

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

For a simple read tool with one parameter and no output schema, the description sufficiently conveys the tool's purpose and the data it returns (owner, status, dates, DNS provider, nameservers). It is complete for its scope, and the schema covers the input.

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 single parameter 'domain' is fully documented in the input schema with a description ('Domain name (e.g. "example.com")'), providing 100% schema coverage. The description adds no additional parameter semantics beyond this, so the baseline of 3 is appropriate.

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?

The description clearly states a specific action ('Get') and target resource ('detailed info about a domain'), enumerating the data fields (owner, status, dates, DNS provider, nameservers). This distinguishes it from sibling tools like namecheap_get_dns_hosts or namecheap_get_nameservers, which focus on subsets.

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?

The description implies usage by listing the comprehensive info returned, but it does not explicitly state when to use this tool over alternatives like namecheap_get_nameservers or namecheap_get_dns_hosts, nor any exclusion cases. The guidance is implied rather than explicit.

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