StackWiz MCP Server

update_dns_proxy

Enable or disable Cloudflare proxy for a subdomain's DNS record, controlling whether traffic routes through Cloudflare's network.

Instructions

Enable or disable Cloudflare proxy for 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>",
      "enable": "<enable>"
    },
    "name": "update_dns_proxy"
  }
}

Input Schema

Name	Required	Description	Default
`enable`	Yes	True to enable proxy, False to disable
`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

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It indicates a mutation ('Enable or disable') but does not disclose side effects, required permissions, error behavior on non-existent subdomains, or any rate limits. The absence of these details is a significant gap for a state-changing tool.

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 a single, compact sentence that directly states the tool's function without redundant phrasing. It is front-loaded with the action and object.

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 low complexity (two parameters, simple boolean toggle) and presence of an output schema, the description covers the core purpose. However, it doesn't mention what happens if the subdomain doesn't exist or whether changes propagate immediately, which would enhance completeness. Still, it is largely sufficient for a simple tool.

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?

The schema provides descriptions for both parameters (subdomain and enable) with 100% coverage. The description adds the context of 'Cloudflare proxy' but does not enrich parameter meaning beyond what the schema already states. Baseline of 3 is appropriate given full schema coverage.

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 uses a specific verb ('Enable or disable') and a clear resource ('Cloudflare proxy for a DNS record'). It clearly differentiates from sibling tools like create_dns_record, delete_dns_record, and list_dns_records by focusing on the proxy toggle action.

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 for toggling proxy state on an existing DNS record, but it does not explicitly state when to use this tool versus alternatives such as create_dns_record or delete_dns_record. No exclusions or prerequisites are mentioned.

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

Deploy Server