Skip to main content
Glama

Set WHOIS privacy

set_whois_privacy
Idempotent

Hide or show the owner's name, email and address in the public WHOIS and RDAP output of a domain; when hidden, a privacy contact is published instead. Ownership, DNS and transfers are not affected (transfers: set_transfer_lock). Some TLDs reject the setting, for example .de, .eu, .nl, .be and .uk; 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>",
      "enabled": "<enabled>"
    },
    "name": "set_whois_privacy"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe domain ID
enabledYestrue hides the owner's contact data, false publishes it

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the safety profile (non-destructive, idempotent write), and the description adds substantive behavior on top: a privacy contact is published when hidden, ownership/DNS/transfers are unaffected, and certain TLDs cause the call to fail. Failure mode and blast radius are both disclosed.

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 tightly written sentences, front-loaded with the effect, followed by side effects, failure conditions, and a pointer to the state-check tool. Every clause carries actionable information.

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 two-parameter idempotent mutation with no output schema, the description supplies everything needed: what changes, what does not change, the substitution behavior, and the conditions under which the call fails.

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 both 'id' and 'enabled' are already documented including the true/false meaning. The description restates the same semantics in prose but adds no format, ordering, or edge-case guidance for the parameters, so the baseline 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 and resource ('Hide or show the owner's name, email and address in the public WHOIS and RDAP output') and immediately names the sibling it must not be confused with (set_transfer_lock for transfers, get_domain for state checks). An agent can distinguish this from every listed sibling without opening a schema.

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?

Gives clear routing ('Check the current state with get_domain') and defers transfer-related changes to set_transfer_lock, plus an explicit exclusion list of TLDs that reject the setting. It stops short of stating outright when not to use the tool, but the effective coverage is high.

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.