Skip to main content
Glama
Fewsats

Sherlock Domains MCP

by Fewsats

set_contact_information

Configure contact details for domain purchases and ICANN registration, including name, email, address, and location information required before buying domains.

Instructions

Set the contact information that will be used for domain purchases and ICANN registration.
Contact information must be set before attempting any domain purchases.

All fields are required:
    first_name: First name
    last_name: Last name
    email: Email address
    address: Street address
    city: City
    state: Two-letter state code for US/Canada (e.g., 'CA', 'NY') or province name (e.g., 'Madrid')
    postal_code: Postal code
    country: Two-letter country code ('US', 'ES', 'FR')

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cfnYes
clnYes
cemYes
caddYes
cctYes
cstYes
cpcYes
ccnYes
Behavior3/5

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

With no annotations provided, the description carries the full burden. It clearly indicates this is a write/mutation operation ('Set') with permanent effects (for domain registration). However, it doesn't disclose important behavioral traits like whether this requires specific permissions, if changes are reversible, what happens to existing contact information, or any rate limits/quotas.

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?

The description is efficiently structured with a clear purpose statement upfront, followed by prerequisite information, then a well-organized parameter explanation. Every sentence adds value with no redundant information. The bullet-style parameter listing is particularly effective for clarity.

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 mutation tool with 8 parameters and no annotations or output schema, the description does an excellent job explaining purpose, prerequisites, and parameter semantics. The main gap is lack of information about the return value or confirmation of success/failure, which would be helpful since there's no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage (all parameters have generic titles like 'Cfn'), but the description provides comprehensive semantic mapping for all 8 parameters. It clearly explains what each parameter represents (e.g., 'first_name: First name', 'state: Two-letter state code...'), including format requirements and examples, fully compensating for the schema's deficiencies.

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 specific action ('Set the contact information') and its purpose ('used for domain purchases and ICANN registration'). It distinguishes this from sibling tools like 'get_contact_information' by specifying it's a set/write operation rather than a read operation.

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?

The description explicitly states when to use this tool ('must be set before attempting any domain purchases'), providing clear prerequisites. It also implies when not to use it (if contact information is already set or if only reading is needed, use 'get_contact_information' instead).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Fewsats/sherlock-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server