Skip to main content
Glama
Sign In
namecheap-webui-mcp

namecheap-webui-mcp

by Microck
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

namecheap_domain_set_feature

Enable or disable auto-renew, domain lock, or WHOIS privacy on a Namecheap domain.

Instructions

Set a Domain Manage feature toggle (auto-renew, domain-lock, whois-privacy).

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": {
      "domainName": "<domainName>",
      "feature": "<feature>",
      "enabled": "<enabled>"
    },
    "name": "namecheap_domain_set_feature"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNameYesFull domain name, for example example.com
featureYesFeature toggle to change.
enabledYesTarget state for the feature toggle.
headedNoRun with a visible browser window.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations exist, so the description must disclose behavior. It only states 'Set a ... feature toggle' indicating a mutation, but fails to mention required permissions, rate limits, side effects (e.g., whois privacy propagation delay), or error cases. Minimal 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?

Single sentence of 14 words, front-loaded with verb and resource. No filler or redundant information.

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 4 parameters, no output schema, and no annotations, the description is too sparse. It does not explain return values, prerequisites (e.g., domain ownership), or error handling. For a mutation tool, more behavioral context is essential.

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%, with each parameter having a clear description. The tool description adds no new information beyond listing the features; the schema already defines domainName, feature, enabled, and headed adequately. Baseline score of 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?

The description clearly states the verb 'Set' and the resource 'Domain Manage feature toggle', listing specific features (auto-renew, domain-lock, whois-privacy). This distinguishes it from siblings like 'namecheap_domain_get_features'.

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 for toggling features but provides no explicit guidance on when to use this tool versus alternatives like 'namecheap_domain_get_features' or 'namecheap_dashboard_list_options'. No exclusions or prerequisites mentioned.

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