Skip to main content
Glama
Fewsats

Sherlock Domains MCP

by Fewsats

domains

List domains owned by the authenticated user, showing registration details, expiration dates, nameservers, and management settings.

Instructions

List domains owned by the authenticated user.
Each domain object contains:
    id (str): Unique domain identifier (domain_id in other methods)
    domain_name (str): The registered domain name
    created_at (str): ISO timestamp of domain creation
    expires_at (str): ISO timestamp of domain expiration
    auto_renew (bool): Whether domain is set to auto-renew
    locked (bool): Domain transfer lock status
    private (bool): WHOIS privacy protection status
    nameservers (list): List of nameserver hostnames
    status (str): Domain status (e.g. 'active')

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes the tool as a read-only list operation (implied by 'List domains'), and it details the structure of returned domain objects, including fields like 'id', 'domain_name', and 'status'. This adds valuable context beyond basic functionality, though it doesn't cover aspects like error handling or authentication requirements explicitly.

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 appropriately sized and front-loaded: the first sentence states the core purpose, followed by a bulleted list of return fields for clarity. Every sentence earns its place by providing essential information without redundancy or fluff.

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?

Given the tool's low complexity (0 parameters, no output schema, no annotations), the description is quite complete. It explains what the tool does, who it applies to (authenticated user), and the structure of returned data. However, it could be slightly more complete by mentioning any limitations (e.g., pagination) or error cases, though this is minor for a simple list tool.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, so no parameter information is needed from the description. The description correctly focuses on output semantics by detailing the returned domain object fields, which compensates for the lack of an output schema. This adds significant value beyond the input schema.

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 ('List') and resource ('domains owned by the authenticated user'), making the purpose specific and unambiguous. It distinguishes this tool from siblings like 'search' or 'get_purchase_offers' by focusing on listing owned domains rather than searching or purchasing.

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 by specifying 'domains owned by the authenticated user,' which suggests this tool is for retrieving the user's own domains. However, it does not explicitly state when to use this tool versus alternatives like 'search' or provide any exclusions or prerequisites, leaving some guidance gaps.

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