Squish

Set my cdn

set_my_cdn

Turns the CDN (edge cache in front of the site) on or off for one of the customer's hosting sites. This rewrites the domain's DNS on Squish nameservers, so it takes a few minutes to settle and is refused for a domain whose DNS is managed at another registrar. Two-step: (1) confirm:false previews the change; (2) ONLY after an explicit yes in their most recent message, call with confirm:true. The result says what HAPPENED (cdnEnabled), which can differ from what was asked — relay the note when there is one.

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": {
      "domain": "<domain>",
      "enabled": "<enabled>"
    },
    "name": "set_my_cdn"
  }
}

Input Schema

Name	Required	Description
`domain`	Yes	The hosted site's domain.
`confirm`	No	false (default) returns the preview; true applies. Pass true ONLY after explicit user confirmation.
`enabled`	Yes	true to turn the CDN on, false to turn it off.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description discloses the side effect (domain DNS is rewritten), the settling delay of a few minutes, the refusal condition for externally-managed DNS, and that the response reports what happened via cdnEnabled which may differ from the request. It even instructs relaying a `note` field, which the agent could not infer from the flat annotations.

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 tight sentences ordered by importance: what it does and its side effects first, the safety protocol second, the result-interpretation caveat last. There is no filler and no restatement of the tool name or annotations.

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

Completeness5/5

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

With no output schema, the description correctly supplies the return-value contract (cdnEnabled reflects actual state, note may be present). Combined with the two-step protocol and DNS precondition, an agent has everything needed to call this mutation safely and interpret the outcome.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description nevertheless adds meaning the schema does not, namely that confirm:true is gated on an explicit affirmative in the most recent user message rather than merely "user confirmation". It does not add anything about `domain` or `enabled` beyond what the schema already says.

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?

"Turns the CDN (edge cache in front of the site) on or off for one of the customer's hosting sites" gives a specific verb (toggle), a specific resource (CDN on a hosted site), and parenthetically defines what the CDN is. It is clearly distinguishable from siblings like get_my_cdn_stats (read stats) and purge_my_cdn_cache (invalidate cache).

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

Usage Guidelines5/5

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

It states exactly when to call each parameterization: confirm:false for a preview, confirm:true only after an explicit yes in the user's most recent message. It also states a hard precondition (DNS must be on Squish nameservers) and the resulting refusal case, so the agent knows before calling whether the operation can succeed.

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

All Squish tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?