namecheap-api-mcp

set_registrar_lock

Lock a domain at the registrar for theft protection, or unlock it before initiating an outbound transfer.

Instructions

Lock or unlock a domain at the registrar (theft protection). Unlock before initiating an outbound transfer.

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

Input Schema

Name	Required	Description	Default
`domain`	Yes	Full domain name, e.g. example.com
`action`	No	LOCK or UNLOCK. Default LOCK.	LOCK

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 22, 2026

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 full burden. It discloses that the tool mutates registrar lock state, but does not mention potential side effects, propagation delays, required permissions, or irreversible consequences.

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?

Two sentences, no redundant information. The first sentence defines the tool, the second gives a critical usage hint. Every word earns its place.

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?

No output schema exists, yet the description does not explain what the tool returns (e.g., confirmation, status). For a simple mutation tool, this is a moderate gap; agent cannot anticipate the response format.

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%, so baseline is 3. The description adds context for the action (unlock before transfer) but does not provide new semantic details beyond the schema's enumerated values and defaults.

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 'Lock or unlock' and the resource 'domain at the registrar', with a specific purpose of theft protection. It distinguishes from siblings like get_registrar_lock (read-only) and other set_* tools.

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

Usage Guidelines4/5

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

The description provides a clear usage hint: 'Unlock before initiating an outbound transfer.' It implies when to use but does not explicitly state when not to use or list specific alternatives beyond the sibling context.

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

Deploy Server