Skip to main content
Glama
Sign In
domain-setup-mcp

domain-setup-mcp

by anasmughal239-alt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

domain_apply

Destructive

Apply a saved DNS plan to Cloudflare in atomic per-domain batches. Skips domains changed since planning and returns a run_id for rollback.

Instructions

Apply a saved plan to Cloudflare. Each domain's DNS changes go in one atomic batch (all or nothing). Skips any domain whose DNS changed since the plan was made. Returns run_id for domain_rollback.

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": {
      "plan_id": "<plan_id>"
    },
    "name": "domain_apply"
  }
}

Input Schema

NameRequiredDescriptionDefault
onlyNoApply to a subset of the plan's domains.
confirmNoFalse = dry run. True writes to Cloudflare. Requires user approval.
plan_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=false and openWorld=true, so the safety bar is lower. The description still adds real value: all-or-nothing per-domain batching, an automatic skip for domains whose DNS drifted since planning, and the run_id handoff to rollback. Missing only auth/permission expectations and cross-domain partial-failure behavior.

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?

Three sentences, front-loaded with the action, then the atomicity guarantee, then the safety skip and return handoff. No filler or repetition.

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 destructive, non-idempotent write with no output schema, the description covers the critical facts an agent needs: atomicity, the drift guard, and the returned run_id used for rollback. It stops short of naming permission requirements or describing the dry-run response, which keeps it from a 5.

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 67%: only and confirm are already documented in the schema, and the description does not elaborate on either (it never explicitly states that confirm=false is a dry run). plan_id carries no schema description, and the phrase 'saved plan' only weakly signals that it references an id from domain_plan.

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?

States a specific verb and resource (apply a saved plan) plus the target system (Cloudflare), and the closing sentence points at the sibling it pairs with (domain_rollback). An agent can tell this apart from domain_plan/domain_audit without opening a schema.

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 drift-skip sentence implies when a plan must be regenerated rather than applied, and the run_id mention implies when rollback is the follow-up. But there is no explicit 'use this when / use domain_plan instead' routing, so the agent must infer the sequencing.

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

Deploy Server

Other Tools