Skip to main content
Glama
Fewsats

Sherlock Domains MCP

by Fewsats
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

create_dns

Add DNS records to domains by specifying type, name, value, and TTL to configure domain routing and services.

Instructions

Create a new DNS record for a domain.

domain_id: Domain UUID (e.g., 'd1234567-89ab-cdef-0123-456789abcdef')
type: DNS record type ('A', 'AAAA', 'CNAME', 'MX', 'TXT', etc.)
name: Subdomain or record name (e.g., 'www' creates www.yourdomain.com)
value: Record value (e.g., IP address for A records, domain for CNAME)
ttl: Time To Live in seconds (default: 3600)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domain_idYes
typeNoTXT
nameNotest
valueNotest-1
ttlNo

Implementation Reference

  • src/sherlock_mcp/server.py:168-179 (handler)
    MCP tool handler function for creating a DNS record. It delegates to the Sherlock client's _create_dns_record method after handling the response uniformly.
    @mcp.tool()
async def create_dns(domain_id: str, type: str = "TXT", name: str = "test", value: str = "test-1", ttl: int = 3600):
    """
    Create a new DNS record for a domain.

    domain_id: Domain UUID (e.g., 'd1234567-89ab-cdef-0123-456789abcdef')
    type: DNS record type ('A', 'AAAA', 'CNAME', 'MX', 'TXT', etc.)
    name: Subdomain or record name (e.g., 'www' creates www.yourdomain.com)
    value: Record value (e.g., IP address for A records, domain for CNAME)
    ttl: Time To Live in seconds (default: 3600)
    """
    return handle_response(get_sherlock()._create_dns_record(domain_id, type, name, value, ttl))
  • src/sherlock_mcp/server.py:168-168 (registration)
    Registration of the 'create_dns' tool using the FastMCP decorator.
    @mcp.tool()
  • src/sherlock_mcp/server.py:169-178 (schema)
    Function signature and docstring defining the input schema (parameters with types and defaults) and descriptions for the 'create_dns' tool.
    async def create_dns(domain_id: str, type: str = "TXT", name: str = "test", value: str = "test-1", ttl: int = 3600):
    """
    Create a new DNS record for a domain.

    domain_id: Domain UUID (e.g., 'd1234567-89ab-cdef-0123-456789abcdef')
    type: DNS record type ('A', 'AAAA', 'CNAME', 'MX', 'TXT', etc.)
    name: Subdomain or record name (e.g., 'www' creates www.yourdomain.com)
    value: Record value (e.g., IP address for A records, domain for CNAME)
    ttl: Time To Live in seconds (default: 3600)
    """

Tool Definition Quality

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits like authentication requirements, rate limits, error conditions, whether the operation is idempotent, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is a significant gap.

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?

The description is appropriately sized and front-loaded with the core purpose in the first sentence. Each subsequent line adds necessary parameter details without redundancy. However, the parameter explanations could be slightly more structured (e.g., bullet points).

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

Completeness2/5

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

Given the tool's complexity (mutation with 5 parameters), lack of annotations, and no output schema, the description is incomplete. It covers parameters well but misses critical behavioral context (e.g., permissions, side effects, response format), making it inadequate for safe agent invocation.

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 description adds substantial meaning beyond the input schema, which has 0% description coverage. It explains each parameter's purpose with examples (e.g., domain_id as UUID, type with record types, name as subdomain, value with IP examples, ttl with default). This fully compensates for the schema's lack of documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates a new DNS record for a domain, specifying both the action (create) and resource (DNS record). It distinguishes from siblings like delete_dns and update_dns by focusing on creation, but doesn't explicitly differentiate from other creation tools (none listed).

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives is provided. The description doesn't mention prerequisites (e.g., needing an existing domain), exclusions, or comparisons to sibling tools like update_dns or dns_records, leaving the agent to infer usage context.

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