StackWiz MCP Server

create_dns_record

Create a DNS record for any subdomain by specifying the record type, value, Cloudflare proxy setting, and MX priority. Automate DNS configuration for your services.

Instructions

Create a DNS record

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": {
      "subdomain": "<subdomain>"
    },
    "name": "create_dns_record"
  }
}

Input Schema

Name	Required	Description	Default
`type`	No	Record type (A, CNAME, MX, TXT)	A
`value`	No	Record value (AUTO for server IP)	AUTO
`proxied`	No	Enable Cloudflare proxy
`priority`	No	Priority for MX records
`subdomain`	Yes	Subdomain name

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, and the description fails to disclose behavioral traits such as idempotency, overwrite behavior, or requirement for specific parameters. For a mutation tool, this lack of transparency 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 a single, efficient sentence that conveys the core purpose without wasted words. However, it is so terse that it omits potentially useful context, though this is acceptable given its simplicity.

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?

Despite the existence of an output schema and full parameter documentation, the description is incomplete for a mutation tool. It lacks any behavioral context, such as what happens if a record already exists or whether special permissions are needed, leaving the agent with insufficient guidance.

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 coverage is 100%, so the baseline of 3 applies. The description adds no extra meaning beyond the schema's parameter descriptions, but it does not need to compensate for missing schema information.

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 action (create) and the resource (DNS record), distinguishing it from sibling tools like list_dns_records, update_dns_proxy, and delete_dns_record. It is specific and immediately understandable.

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?

The description provides no guidance on when to use this tool versus alternatives, nor any prerequisites, side effects, or conditions. It is a bare statement with no usage context.

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

Deploy Server