Skip to main content
Glama
Sign In
mcp-cloud-deploy

mcp-cloud-deploy

by hoangtrietdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

attach_custom_domain

Bind a custom domain to a Cloudflare Pages project and create the matching CNAME in an available Cloudflare DNS zone.

Instructions

Bind a custom domain to a Cloudflare Pages project and create a CNAME in a matching Cloudflare DNS zone when available.

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": {
      "project_name": "<project_name>",
      "domain": "<domain>"
    },
    "name": "attach_custom_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesFully qualified custom domain, for example app.example.com.
project_nameYesTarget Cloudflare Pages project name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full load. It does disclose an important side effect beyond the stated action — automatic CNAME creation in a matching Cloudflare DNS zone — which is genuinely valuable. However, it omits permissions/scopes needed, idempotency, what happens when no matching zone exists or the domain is already attached, and whether the CNAME creation can fail independently of the binding.

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?

A single front-loaded sentence with the primary action first and the conditional side effect second. No filler or redundant restatement of the tool name.

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

Completeness3/5

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

For a two-parameter mutation with no annotations and no output schema, the description should say more about failure modes and prerequisites. It covers what the tool does and one side effect well, but leaves an agent unable to predict the result or the conditions under which the DNS step is skipped.

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% and both parameters carry descriptions with patterns and examples, so the schema already does the work. The description only names the concepts 'custom domain' and 'project' without adding format, scope, or constraint detail. Baseline 3 applies.

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?

States a specific verb and resource — 'Bind a custom domain to a Cloudflare Pages project' — plus a secondary effect (CNAME creation). It is clearly distinguishable from the deployment-oriented siblings, though it never explicitly says so.

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?

Usage is only implied: an agent can infer this is the step after a project exists, but there is no statement of prerequisites (project must already exist, domain must not already be bound) and no explicit when-not guidance. 'When available' hints at conditional behavior without explaining the condition.

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