Skip to main content
Glama

Set domain transfer lock

set_transfer_lock
Idempotent

Lock or unlock a domain against transfers to another registrar. Keep it locked unless the user is moving the domain away: then unlock it here and get the auth code with get_authcode. Lock it again when the transfer is done or called off. DNS, renewal and WHOIS are not affected. Some TLDs have no transfer lock; the call then fails. Check the current state with get_domain.

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": {
      "id": "<id>",
      "locked": "<locked>"
    },
    "name": "set_transfer_lock"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe domain ID
lockedYestrue blocks transfers away from Sitequest, false allows them

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish that this is a mutating but idempotent, non-destructive operation; the description adds value beyond that by naming what is NOT affected (DNS, renewal, WHOIS) and disclosing a real failure mode (some TLDs have no transfer lock, so the call fails). It stops short of stating authorization requirements or the shape of the failure response, which keeps it off a 5.

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?

Front-loaded with the operation, then workflow, then side effects, then failure mode. Nearly every clause carries information; the sequence is logical and there is no filler, though the workflow sentences are slightly dense and could be split for scanning.

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

Completeness4/5

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

For a two-parameter boolean setter with no output schema and full annotation coverage, this covers purpose, ordering, side effects, and a known failure case. The only omission is what a successful response confirms, which is minor given idempotentHint and the absence of an output schema.

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%, and the schema already spells out that `locked=true` blocks transfers away and `false` allows them, plus the ID format. The description's "lock or unlock" framing adds no syntax or conditional detail beyond that, so the baseline 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?

States a specific verb pair and resource: "Lock or unlock a domain against transfers to another registrar." This distinguishes it immediately from transfer_domain, get_authcode, and set_nameservers among the siblings without needing to open any schema.

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

Usage Guidelines5/5

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

Explicit when/when-not guidance: keep locked by default, unlock only when the user is moving the domain away, and re-lock when the transfer completes or is cancelled. It also routes the agent to named siblings for adjacent steps (get_authcode for the auth code, get_domain to check current state).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.